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

Hi we're trying to use esc in conjunction with the automation api (similar to <https://pulumi-community.slack.com/archives/C0602S4P4T1/p1707159338847029>) but it doesn't appear to be decrypting secrets?

Hello Liam! Can you give some more context, is it when you pulumi up that the secrets are not working?

We're trying to retrieve via GetAllConfig in the ts auto api.

Can you an outline of your environment config and stack config?

Hey <@U01GS450UP5>! This currently doesn't quite work as you would expect. There's an <https://github.com/pulumi/pulumi/issues/14770|issue> to introduce a flag to `pulumi config` that would allow opening the environment, which would then need to be absorbed into automation api to unlock the behavior you're describing. Currently, it's only possible to gain the decrypted value of the secret from within the pulumi program, but not from automation api.

<@U01GS450UP5> this should be supported in the next release <https://github.com/pulumi/pulumi/pull/15469>