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

Could you raise a bug about this at <http://github.com/pulumi/pulumi|github.com/pulumi/pulumi> if the stacks are setup for kms they shouldn't be asking for passphrases. If you know what command flow is repro'ing this we can hopefully fix it up quickly.

Not necessary. I found that the remote state had a passphrase configured (initially started with passphrase).
Using the initially used passphrase and
`pulumi stack change-secrets-provider "awskms:...` fixed it apparently