https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
f
The stack that I created was using secret outputs
w
Cc @bitter-oil-46081 for pointer to docs on this.
b
@faint-vegetable-61837 When you were managing this stack with the Pulumi service, you were using the default secrets provider (i.e. you did not have type in a passphrase on each operation, and the encryption was managed by the Pulumi service for you)?
f
Yes, thats right, we were just using --secret option without setting a passphrase
b
Okay - Thanks. The state file you are trying to import, it should have a 
secrets_providers
section in it, does it? If so, does the object have a 
type
member?
FWIW - I don't believe we have a good story here for moving from the service to the local backend when using secrets. The crux of the issue is when you 
pulumi stack export
a stack, all of the secret values are going to be encrypted with a key managed by the pulumi service, and the local backend is not going to understand how to interact with these keys. I think this is something we can support however. My previous question is related to me trying to understand how we could have gotten the error you ended up getting (the fact that the there's no name after 
type
in that message is confusing to me)
Open in Slack
PreviousNext
Powered by