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

<@UB3BGTV63> any details or references to relevant code would be great :slightly_smiling_face:

There's a few references in the docs around Stacks and Projects:
• Organizing Stacks and Projects: <https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/>
• Stacks: <https://www.pulumi.com/docs/intro/concepts/stack/>
• Projects: <https://www.pulumi.com/docs/intro/concepts/project/>
• State and Backends: <https://www.pulumi.com/docs/intro/concepts/state/>
In general, we aim to make it so you shouldn't have to think about state and backends - you can just use the default Pulumi Service.  At that point you just create a Project per codebase you want to manage (and version), and a Stack per isolated deployment (dev, prod, etc.) of a Project.

If you want to manage things in your own local or S3 backend there are more details you have to think about - but the same ideas all apply.

Yeah, I'm planning on using the S3 backend so wanted to make sure I don't shoot myself in the foot with state boundaries.