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 don't think `stack select` actually validates the passphrase is correct, so might just be you've got a typo that only preview is catching.
For issue two you might be able to export the state and remove and secret objects (they have a key "4dabf18193072939515e22adb298388d" with value "1b47061264138c4ac30d75fd1eb44270") and remove the password config and salt from the stack config. But I'd take backups of state and config before trying that.

<@U02J3T6A8LB> from my experience `stack select` actually does validate. it fails when performing it with a different passphrase. In addition, when failing regarding the passphrase I usually get a different error msg.

regarding issue number two - great, this is one of the workarounds I had in mind. Thank you:pray:!

Could you raise an issue for 1 on github, I think I've heard this mentioned before and it would be good to have something to track it. If you work out how to reproduce the issue that would be amazing, but not necessary to open the issue.

<@U02J3T6A8LB> hi, so i think i might be doing something g wrong while editing the stack, I removed the whole "secrets_providers" path, and I noticed there is multiple objects with this "4dabf18193072939515e22adb298388d" key-value combination. should I remove everything that is associated with it and then perform a refresh ?

Yeh if you've forgotten the passphrase we don't have anything built in to fix this, but I think just clearing all secret objects out of state and running refresh should trigger the engine to ask for a new passphrase and re-encrypt everything.