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

As <@UB8A66MPS> noted, the current recommendation is to export these from the lower level, and then set them as `config` in the higher level project.

This of course isn't quite as smooth as we'd like, and we have many ideas for how to improve here.  In particular, we'd love to be able to have the higher level program directly reference exports of a stack, and enforce constraints on the lower level stack that these don't change without acknowledgement (or even cascading mututal deployments) from the higher level stack.