I have a project with 2 stacks I m exporting a rather large

Question

I 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 up`

little-cartoon-10569 · Answer

Dependencies 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 · Answer

You need the ` suppress outputs` option for this btw

ambitious-afternoon-55254 · Answer

So Stack A controls DNS Stack B is just another env I need to export some AWS ACM DNS records for automatic cert verification

little-cartoon-10569 · Answer

I recommend moving DNS to another project that must be deployed before any stacks in this project

little-cartoon-10569 · Answer

Have all stacks in the current project be dependent on the only stack in the DNS project

ambitious-afternoon-55254 · Answer

Does pulumi support inter project dependencies

little-cartoon-10569 · Answer

Absolutely

little-cartoon-10569 · Answer

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

ambitious-afternoon-55254 · Answer

Ok this sounds like exactly what I need

ambitious-afternoon-55254 · Answer

Do you happen to know off hand a good starting place in the docs for me to look at

little-cartoon-10569 · Answer

Generally 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 · Answer

There is a page of recommendations about this iirc onesec

little-cartoon-10569 · Answer

ambitious-afternoon-55254 · Answer

Thank you