This message was deleted.

sparse-intern-71089

07/23/2019, 12:40 PM

This message was deleted.

colossal-beach-47527

07/23/2019, 3:58 PM

I might be wrong, but I don’t believe you can. I think you’d need to remove all of your configuration values and then readd them using a new passphrase.

bored-river-53178

07/23/2019, 5:07 PM

well, that's unexpected

bored-river-53178

07/23/2019, 5:07 PM

but are you sure that it only affects the config itself

bored-river-53178

07/23/2019, 5:07 PM

(as opposed to a state file)

colossal-beach-47527

07/23/2019, 5:42 PM

sure that it only affects the config itself

Yes. (Assuming I’m understanding you correctly.) The passphrase is used to encrypt/decrypt configuration values. But those configuration values themselves aren’t put in the state file. Though I’ll cc @microscopic-florist-22719 to keep me honest here. Since I’m not sure how the “pluggable secrets” work we did recently does or does not interact here.

microscopic-florist-22719

07/23/2019, 6:39 PM

The passphrase affects both configuration secrets and secrets stored in the checkpoint file.

microscopic-florist-22719

07/23/2019, 6:39 PM

We plan to enable passphrase changes this sprint.

👍🏽 3

447 Views

Open in Slack

Previous Next

Pulumi Community

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.