This message was deleted.
# general
s
This message was deleted.
b
Hi @clever-plumber-29709 you need to invoke project B - Pulumi doesn’t assume that you want to coordinate these operations as you may need to coordinate how things work between projects I can suggest you look into “automation-api” if you want to build some coordination between projects as part of a Pulumi apply
c
But is there a best practice for this cases? having this stack reference creates a dependency between the stacks, and if we have to manually check each change for possible cascade effects on outputs it could really get cumbersome
e
I was reading about this a couple of days ago and came across https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/ maybe it'll help you
c
I knwo well that doc, but it dosent help me, i'm not talking about organicin,g but more about how dependencies are managed when you use stack outputs on another projects. seems like is a good feature but is not really practical on the real world