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

Think about it this way - your pulumi code represents a way of building something. You ideally want to build it the same way in development and production - but perhaps have smaller scale in development.

a pulumi project maps to the pulumi code pretty much - so having multiple stacks for multiple environments for a single project makes sense - that way a fix in development can be easily and correctly applied to production because you've tested the pulumi code there first and the original code for both environments were the same :slightly_smiling_face:

when I mention multiple projects for multiple types of operations- I usually think about this in terms of layers of stuff.. baseline infra established in one project, then one project manages database configurations, another project manages kubernetes configurations, and you might have a seperate project for access management (I'm currently playing with pulumi automation for this purpose, it shows real promise! :D)