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

Hello. Just starting a new K8S/microservice project with Pulumi. How do I set it up so that I have three stacks (local, test, prod), where state for local is somehow stored on each engineer's system (preferably in the project root), but test and prod are in Pulumi Cloud? Is that the appropriate way to do it? (edited)

I assume the "local" stack is independent for each developer and they deploy against a local target (or an environment exclusively owned by them)? And the developers are not deploying to test and prod from their local machines?

In this case, every developer could have their own project with the local file system as the backend, and your test/prod deployments can share a project with Pulumi Cloud as the backend.

Yes. They would deploy locally to Kind. So, the best way to do this would be separate projects?

The developers locally `pulumi login` to their file system, while your test/prod deployment workflows `pulumi login` to Pulumi Cloud. Usually, you'd store the backend config in the `Pulumi.yaml` file that defines the Pulumi project, but if I read<https://www.pulumi.com/docs/iac/concepts/state-and-backends/#logging-into-and-out-of-state-backends| the docs> correctly, you don't have to do that. So you can share one `Pulumi.yaml` project configuration with everyone and don't need to maintain two different versions of the file as I initially assumed.