This message was deleted.
# generals
sparse-intern-71089
11/21/2023, 2:22 PMThis message was deleted.
l
little-cartoon-10569
11/21/2023, 7:17 PMThis sounds like a case for projects, not stacks. Since you would deploy this once and once only, it is on a different deployment schedule to something like your networks (which might get redeployed whenever you add an AZ or change your WAF) or ECS service (which might get redeployed every time your build pipeline succeeds).
☝️ 1
👍 1
m
millions-pharmacist-626
11/21/2023, 9:45 PMThanks for the insights!
g
gentle-application-59272
11/22/2023, 8:18 AMWe have many projects, some are foundational, such as the stuff for our aws networks and this is all 1 stack that deploys to multiple accounts and regions. Other projects configure other platforms, and finally our app projects define resources for a given app with each stack being resources for swimlanes such as production, staging etc
gentle-application-59272
11/22/2023, 8:19 AMAnd we use typescript’s Zod to define runtime type checkers and derived static types in a regular typescript ‘lib/‘ package to coordinate pulumi outputs between projects
gentle-application-59272
11/22/2023, 8:19 AMIt works well but there is always the issue of projects depending on projects creating a dependency graph
s
stocky-restaurant-98004
11/22/2023, 6:46 PMI agree with @little-cartoon-10569 - use case for projects.
s
salmon-account-74572
11/28/2023, 10:42 PMThis blog post may also help: https://www.pulumi.com/blog/iac-recommended-practices-structuring-pulumi-projects/
m
millions-pharmacist-626
11/29/2023, 8:01 AMThanks everyone for the great insights!