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

Hey, I've run in to an issue where I can't see one of my stacks with `pulumi stack ls` unless `PULUMI_CONFIG_PASSPHRASE` is set, I'm using the s3 backend and the passphrase secrets provider. Output of `pulumi --logtostderr -v5 stack ls` below:
```I0324 18:37:18.745036   38931 backend.go:859] error reading stack: staging (decrypting secret value: failed to decrypt: incorrect passphrase, please set PULUMI_CONFIG_PASSPHRASE to the correct passphrase) skipping
NAME         LAST UPDATE  RESOURCE COUNT
management*  3 weeks ago  32```
Does anyone have any ideas? I can't `pulumi up` right now because there's a reference to the staging stack and the passphrase is different :sweat_smile: