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

I was pleasantly surprised when Pulumi ESC was released, especially because `esc env open --format dotenv` corresponds to something we’ve been doing time and again in Pulumi : scripting to get a dotenv that our devs can use locally

Before that, we were copy/pasting .env files on Slack which isn’t great... and most of the time our devs don’t have up-to-date .env files on projects they aren’t actively working on so having a central point of truth was nice


My question is the following : `esc` does replace fetching secrets from a Pulumi stack config, but it can’t obtain stuff from Pulumi’s stack output, can it ?

It would be nice to be able to have stuff like database credentials, domains, etc. in the dotenv created by `esc`

&gt; but it can’t obtain stuff from Pulumi’s stack output, can it?
Not yet - but soon!  This is tracked in <https://github.com/pulumi/esc/issues/90|https://github.com/pulumi/esc/issues/90>. 