This message was deleted.

Just run

pulumi stack change-secrets-provider passphrase

again and it will prompt for the current passphrase and then a new passphrase. You have to run it on every stack in the project though.

Thanks! Unfortunately I don’t have that password. When playing around with that stack I didn’t save it, because I thought its only used in the config.yml. I thought just reverting that would be fine. Unfortunately it seems the salt or some kind of derived key is stored in the state stored in the pulumi backend as well

Ah, if you don't know the current passphrase that is more difficult. If you have access to the state file (i.e. you're using the local backend or an s3/azure backend) you could potentially remove the secrets provider config from the

~/.pulumi/stacks/<stack>.json

file, but I don't know what implications that has.

Unfortunately I am using the pulumi cloud backend.