https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
q
How did you migrate your state?
h
Copy code
pulumi login
pulumi stack select dev
pulumi stack export --show-secrets --file dev.stack.json
pulumi login --local
pulumi stack init dev
pulumi stack select dev
pulumi stack import --file dev.stack.json
@quiet-wolf-18467 most like below, follow the document from https://www.pulumi.com/docs/intro/concepts/state/#migrating-between-backends
I found the "secrets_providers" in local state file was still point to Pulumi server.
Copy code
$ cat .pulumi/stacks/dev.json | jq '.checkpoint.latest.secrets_providers'                       0|PIPE|0 ✔  6s  
{
  "type": "service",
  "state": {
    "url": "<https://api.pulumi.com>",
    "owner": "weiliy",
    "project": "astarter",
    "stack": "dev"
  }
}
q
You can use 
pulumi stack change-secrets-provider
command to switch to another secrets backend also
h
@quiet-wolf-18467 thanks. It works. But need one more step, if I am only login to the local server. It cannot migrate to new secrets-provider, because it did not have access to Pulumi server. I found that it can double login:
Copy code
pulumi login  // login to pulumi server
pulumi login --local // login to local server
pulumi stack change-secrets-provider -s dev passphrase  // migrate from default to passphrase
q
Glad you got it working 🎉
11 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by