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

There is not, unfortunately. You’d have to pass the data to each child’s constructor.

Note that we do inherit some - like `provider` and `protect` down the hierarchy already today.  It's reasonable that we could add something like `.context` on components that gets inherited in a similar way, reaching up to the root of the hierarchy to find a value.

That would though make the interface for a component much less explicit - they would presumably then depend on some ambient `context` being provided.

<@UCPSHLVC4> Curious if you have a design for this in mind that you think would work well?  If so, would be great to open a GH issue with the suggestion to track this (and disucss).