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

The state file itself will still be available in the Pulumi SaaS and other backend types. The entire state is not encrypted, only any values, inputs, outputs, etc that are marked as secret. Config secrets are not recoverable without the original passphrase.

You can potentially migrate your state to a new stack (with new passphrase) by changing the secrets provider. Those steps are detailed at <https://www.pulumi.com/docs/intro/concepts/config/#changing-the-secrets-provider-for-a-stack>. You will need to adjust those steps as you cannot use `--show-secrets` without the passphrase. This will be a manual process, modifying your state file directly, so it might be easier/quicker to start over if this is not a critical stack.

Thanks. It's not essential, I just need to reimport those few resources that I have created before.