This message was deleted.
# generals
sparse-intern-71089
02/23/2023, 12:18 AMThis message was deleted.
l
little-cartoon-10569
02/23/2023, 12:26 AMDependencies between stacks in the same project sounds like a very bad idea to me... how do you deploy stack A in an environment that doesn't have stack B?
little-cartoon-10569
02/23/2023, 12:27 AMYou need the
--suppress-outputsa
ambitious-afternoon-55254
02/23/2023, 12:28 AMSo Stack A controls DNS. Stack B is just another env. I need to export some AWS ACM DNS records for automatic cert verification….
l
little-cartoon-10569
02/23/2023, 12:28 AMI recommend moving DNS to another project, that must be deployed before any stacks in this project.
little-cartoon-10569
02/23/2023, 12:28 AMHave all stacks in the current project be dependent on the only stack in the DNS project.
a
ambitious-afternoon-55254
02/23/2023, 12:29 AMDoes pulumi support inter-project dependencies?
l
little-cartoon-10569
02/23/2023, 12:29 AMAbsolutely.
little-cartoon-10569
02/23/2023, 12:32 AMIt is core to most implementations. It would be common to have projects for base infra + users/auth (deployed almost never); shared infra like Config, Orgs and DNS (deployed only when needed); shared app infra like Cognito, buckets and databases (deployed on appropriate feature release); apps (deployed on demand or feature release).
a
ambitious-afternoon-55254
02/23/2023, 12:33 AMOk — this sounds like exactly what I need!
ambitious-afternoon-55254
02/23/2023, 12:33 AMDo you happen to know off hand a good starting place in the docs for me to look at?
l
little-cartoon-10569
02/23/2023, 12:34 AMGenerally, group into projects based on deployment cycles; group into stacks based on location (meaning anything like region, staging vs. prod, dev1 vs. dev2, etc.).
little-cartoon-10569
02/23/2023, 12:35 AMThere is a page of recommendations about this, iirc... onesec...
little-cartoon-10569
02/23/2023, 12:35 AMa
ambitious-afternoon-55254
02/23/2023, 12:37 AMThank you!
👍 1