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

Take a look at stack outputs 

<https://www.pulumi.com/docs/intro/concepts/stack/|https://www.pulumi.com/docs/intro/concepts/stack/>

A common way is by “shelling out” to the Pulumi CLI and just calling `pulumi stack output`, passing the stack and the output as arguments. We do this, for example, to fetch URLs produced by other stacks in the organization, such as here, where <http://pulumi.com|pulumi.com> needs a URL produced by another stack in the organization: <https://github.com/pulumi/docs/blob/0f7f91843ba78fc09b0dfad37fc47b83c2ed08c3/scripts/build-site.sh#L8>

And then the website (a Hugo static site) refers to that environment variable at build-time: <https://github.com/pulumi/pulumi-hugo/blob/3a224af22df190b3f89164237b05ac338d8ed8a9/themes/default/layouts/partials/convert.html#L18>

Ah, of course! I was actually aware of stack outputs, but I never thought of the idea of just simply using the pulumi CLI wherever I need it :smile: Thanks a lot guys!