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

I can’t say there aren’t any other solutions, but this will be a nightmare to move to a modular setup in the future. You would have to do a lot of work by manually manipulating the state.

I would highly advise a single git repo if you want to keep it simpler, but have multiple pulumi projects within it. 1 project per app, and 1 stack per environment.

Thanks for the insight -- it makes sense to break out infra for separate apps, but I'm working on a single platform/system/backend at the moment. Is it a best practice to break out things like the network layer, or monitoring layer into separate projects, even if they are part of the same backend?

I group everything by application. For us an application = a separate repository. I do highly recommend you do this. You do NOT want a huge pulumi project as it will be very slow to work with when applying changes.

I would also definitely separate out stuff like VPCs and such, because you don’t want to be touching that when running changes such as deploying a new version of your application. Critical pieces of the infrastructure need to be worked on with even more care, and it’s best to keep those pieces separated IMO.

Thank you <@UGDSK5RNC> really appreciate it!