No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This sounds like it would be addressed by what we've been calling "dynamic linking" (<https://github.com/pulumi/pulumi/issues/109>)

The Workaround Joe eludes to is that we had some customers that factored their app into multiple layers (a data layer, a networking layer and an app layer, for example) and then would export the AWS IDs of relevant pieces of their infrastructure, and then set these ARNs as config on upstack components.  It works, but its not nearly as slick as what you're describing.

I'd encourage you take a look at the issue and provide feedback there.  It's one of the "big problems" we'd want to go after, but the design still needs to be nailed down.  The design of Pulumi has shifted a lot since October :slightly_smiling_face:.

Oh, that's really interesting! I'll need to mull this over when I have time.

By the way, that GitHub issue mentions y'all are thinking of making this a premium feature. I would advise against that as it so common to share resources between services that are deployed separately. I would instead cap how many separately deployed services a single stack can have