I thought I'd share a bit of my new setup: I've started to use pulumi gitlab provider to set up git projects for my software (I'm both devops and dev at a small company). This is separate from deployment resources - you normally have one gitlab project per software component, but one database (for example) per software component per environment. Obviously I can't keep that together with the code itself - chicken and egg problem, so I have now one separate pulumi project for their build/deploy infrastructure (basically gitlab repo + aws.ECR repo). This evolved to two kinds of component resources - one for projects with OCI (apps) and those without (libs), and now every project starts as one of these. The next thing I want to try is putting pulumi deployment code (ComponentResource classes) together with app code (so that a single git repo has application code and pulumi deployment code), but keep instantiation in a single centralized pulumi project. The reasoning behind this setup is that deployment resources share lifecycle with software releases (roughly), but it's easier to bind everything together in a single pulumi stack. For the context, I have about 300 resources across all production stacks