This message was deleted.
# general
s
This message was deleted.
s
projects are just namespaces for stacks, so your first option seems to make the most sense. That's what we've been doing, and also doing 1 repo per project/stack. That gives good isolation by team for deploy permissions and secrets access.
q
Pulumi stacks can be used in several different ways, which is the reason why the official docs don't settle on a single best practice. It depends on your needs and constraints. We organize it like this (since the project grew into several hundred aws resources in total): • One project per group of resources / resources managed by the same Dev-team • One stack per project for each env • Currently we configure stack dependencies via pulumi config, but you could easily depend allways on the same stack but named like the current env. - in our case we use config because we can mix dev and staging stacks for new features..
g
That’s awesome feedback! Thanks all!!