Channels
#general
Title
# general
a
ambitious-afternoon-55254
02/23/2023, 12:18 AMI have a project with 2 stacks. I’m exporting a rather large output from stack “B” and accessing it in Stack “A” to create some dependency. Is there anyway I can “hide” it so that it doesn’t clutter the output everytime I
pulumi upl
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?
You 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.
Have 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.
It 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!
Do 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.).
There is a page of recommendations about this, iirc... onesec...
a
ambitious-afternoon-55254
02/23/2023, 12:37 AMThank you!