Hey @stocky-butcher-62635! I'd love to help you understand Pulumi a bit. Want to hop into this thread, and we'll see if we can help you get sorted out? 🧵 I'm also happy to hop onto a Zoom call to go over how Pulumi works if that would help.

My initial instinct was to make 1 project with a stack for each environment --

production

,

test

, and maybe feature branches. I think you call this monolithic? The alternative seemed to be to make a project and stacks for every git repository that contains something that gets deployed. But, for example, this would make a web app difficult to configure when it depends on other apps (e.g., HTTP APIs) that are deployed in other stacks of other projects. Is there a way to manage this configuration?

So I personally think of projects and stacks as following the logic of the system and keeping anything that's connected in one project because they often need to be on the same stack for testing or other purposes. So the API infra and the web app infra would be in the same project in your example when I build it. I do define the infra as classes or functions in different files if possible and then import them to the main file just for readability, but that's a Python style. You don't have to if your language of choice doesn't typically do that. If you have the option of doing things this way (your first instinct), I'd do it as I find it saves a lot of heartache in the long run. Some folks keep a sort of control repo that has all of their infra definitions in one place, separate from the application code. I find that to be less than ideal for the same reason I prefer docs to live in the same repo and be treated as code: It's far too easy to update one without considering updating the other. This pattern is often seen with teams that are more separated, though. In the case where you're talking about, the best way to handle that is to export anything that's required to configure something else (e.g., the address for the API) so that it can be used across stacks. We call those things stack references. I'm not the best at C#, to be honest, but we do have some code snippets that might help in the docs here: https://www.pulumi.com/docs/intro/concepts/stack/#stackreferences. You can use stack references across stacks and across projects.