Hello Pulumi Community! I'm transitioning from AWS CDK to Pulumi and looking for guidance on deployment patterns. Background: - Experienced with AWS CDK for infrastructure as code - New to Pulumi but familiar with cloud architecture concepts - Working on a multi-environment setup (dev/staging/prod) What I'm trying to achieve: I need to implement environment-specific deployments with the following requirements: - Isolated stacks per environment (dev, staging, production) - Ability to deploy stacks independently (e.g., deploy only single stack in dev) - Option to deploy multiple environments together when needed - Environment-specific configurations (different instance sizes, regions, etc.) Specific questions: 1. What's the best practice for structuring Pulumi projects for multi-environment deployments? 2. How do you handle environment-specific configurations (similar to CDK context)? 3. Can I use stack references to share resources between environments when needed? 4. Any recommended folder structure or naming conventions? Coming from CDK, I'm used to using context and environment-specific synthesis. What's the Pulumi equivalent? Thanks in advance for any guidance or examples you can share!

The Pulumi docs have some good places to start. Check out https://www.pulumi.com/docs/iac/using-pulumi/organizing-projects-stacks/ for a description of the most common patterns. The "Learn Pulumi" range of mini-tutorials also touches on these areas, and goes into the concept of components in some detail. https://www.pulumi.com/tutorials/learn-pulumi/

Thanks @little-cartoon-10569 for quick response. I believe I have already gone through the resources you shared. Let me also forward the question in #C84L4E3N1 for further discussion.