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

Pulumi separates things like this through configuration, rather than via different codebases or scripts. Then it uses stacks to reprsent a particular deployment with a particular config. That is, your config would control whether app1, app2, both or neither were built &amp; deployed for a particular stack. If you want to add/remove apps to a stack, you change the config and re-run the deployment (for the same stack).

Hope that helps, glad to try and answer more specific questions

Thanks for this. I would imagine that for my case I could build and push each app to ECR separately, then use a single core pulumi "stack" project to deploy all apps to the stack as described above?

Yes, in fact I do something like that, but I don't use pulumi to build/push. Instead, I run codebuild jobs to do all the docker stuff, then the container names are passed into my pulumi program for deployment.

However, I just came across this on the Pulumi site <https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/> and it probably answers the question you are asking. Check out the "micro stacks" section.