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

image.png

I have a stack for each environment, so things are really isolated

to update one env, just run `pulumi stack select myEnv` before

As <@U05TV183P1A> indicated, it’s best to create a separate stack for each environment. Each stack is a separate instance of a Pulumi program plus some associated configuration, and this allows you to have “identical” environments that differ only in configuration details (like different instances in testing versus production, for example). Then, when you want to perform an operation against one of the stacks, use `pulumi stack select &lt;stack&gt;` first, and then run your Pulumi  operation.

A bit OT:
Before moving from Terraform to Pulumi I usually advise considering the team's software engineering strengths - Pulumi requires much more software engineering experience than Terraform and an inexperienced team can easily end up with spaghetti Pulumi from nice Terrafrom.
I've witnessed migrations from TF -&gt; Pulumi and back because the team just did not have enough SWE skills to maintain the code.