This message was deleted.

sparse-intern-71089

05/12/2021, 7:55 PM

This message was deleted.

limited-rain-96205

05/12/2021, 8:01 PM

Found the issue. If you pass the secrets provider in the LocalWorkspaceOptions parameter, it does in fact delete the encryption key (??).

red-match-15116

05/12/2021, 8:03 PM

You’ll need to provide it in both the workspace options and stack settings

red-match-15116

05/12/2021, 8:04 PM

https://github.com/pulumi/automation-api-examples/blob/main/nodejs/inlineSecretsProvider-ts/index.ts#L75-L98

limited-rain-96205

05/12/2021, 9:05 PM

@red-match-15116 Er, sorry if I was unclear. What I'm saying is that if you call

LocalWorkspace.selectStack()

and pass in the secrets provider at all, it will remove the existing encryption key from the stack file.

limited-rain-96205

05/12/2021, 9:08 PM

I resolved the issue by only passing in the secrets provider when doing

LocalWorkspace.createStack()

, and not passing it when doing

LocalWorkspace.selectStack()

limited-rain-96205

05/12/2021, 9:10 PM

However because of this, it looks like secrets encryption is broken if you try to use

LocalWorkspace.createOrSelectStack()

red-match-15116

05/12/2021, 10:46 PM

Ah, got it. That is certainly non-ideal. Could you please open an issue?

13 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.