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

If you consider the apps to be one thing with different flavours, then yes, you could use one project with multiple stacks to achieve this. The only downside would be that you'd need lots of stacks: app1-dev, app1-staging, app1-europe, app1-apac, then app2-**, app3-**, etc. It would become a bit messy to track.

A more common way of achieving this would be to put your reusable code in a ComponentResource(s) and have a project for each app use that code. Each project would have its own stacks.

You could put your ComponentResource(s) in a shared language resource: a jar, dll, NPM package, or whatever.

Thanks! I was indeed leaning more towards that approach, and currently have a stack per app. The reusable code I just listed in a separate package using tsconfig’s references :slightly_smiling_face:

We (Pulumi) have a series of blog posts (starting with <https://www.pulumi.com/blog/iac-recommended-practices-code-organization-and-stacks/>) that may help.