No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I’ve read <https://gist.github.com/clstokes/62d8ff84ada8cd414a88d4f1030f5ddc> on resource adoption but it seems counter-intuitive for me to change my stack to look up the resources, then revert it

I think the other option is to import resources via `pulumi import`
<https://www.pulumi.com/docs/guides/adopting/import/>

This would have to be done for each resource

Feels like it would make sense for Pulumi to add some annotations to resources so that re-importing is easier

Theoretically, that's what refresh should be for

so if there are resources marked as removed from pulumi but still in the cloud....

Refresh should make the state reflect the actual state, right?

certainly by my <https://www.pulumi.com/docs/reference/cli/pulumi_refresh/|reading>

Hm, I wonder if it’s because I changed the `provider`

that could present a problem, different cluster?

Same cluster, but I moved from explicit named provider to the default provider

configured by `config set kubernetes:…`

It’s probably because I’ve done too much at once

I might have a play around and test some of the failure scenarios, manually change state, etc.

quite possibly, unfortunately, pulumi is still a relatively immature product and definitely has some rough edges

I’m using Pulumi mostly for services where I could just recreate them without issue at the moment, but I want to be confident enough to use it for our prod systems

It’s a dream compared to the nightmare that is Helm

And the fact I can still use helm charts and provide them typed values :exploding_head:

oh yeah, it really is a superpower :smile: