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

Hi folks! I have a set of resources that are static and should not change on a per-branch basis like AWS Route 53 hosted zones, CDN distribution, custom domain DNS validation etc, and a set of resources that could change on a per-branch basis like databases, API Gateways and their functions, etc. The static resources would be shared by all of the other per-branch stacks.

Am I correct to model these two resource sets as at least two separate stacks?
Do I need to somehow map a separate `index.ts` with my Pulumi code to each of the two sets of stacks?

I think it would be better to have a separate pulumi project for this.
Make sure to make use of `ComponentResources` to reuse the code.

Thanks for the feedback <@U025964HAJH>. Let me see if I understood:

A project for the static infra as a component resource, and then import that into the other stacks?