busy-toothbrush-9019410/11/2023, 5:27 PM
If I understood correctly then this is due to the secret provider being the pulumi service on the exported stack which is not available with the s3 backend. What is the workaround for this? Do I need to change the secret provider for the stack before exporting it and then use the same provider while importing it or there is any other way where I don't need to change the secret provider in the stack before exporting.
error: could not deserialize deployment: constructing secrets manager of type "service": could not find access token for <https://api.pulumi.com>, have you logged in?
little-cartoon-1056910/11/2023, 10:07 PM
Note:: After migration, your stack’s state will be managed by the Pulumi Cloud backend, but the stack will continue using the same secrets provider. You can separately change the secrets provider for your stack if needed.And that tells you what you need to do, see this bit: https://www.pulumi.com/docs/concepts/secrets/#changing-the-secrets-provider-for-a-stack
busy-toothbrush-9019410/12/2023, 1:55 PM
little-cartoon-1056910/12/2023, 7:04 PM
? You should see that set up in your Pulumi.yaml. I don't know why there isn't an example snippet on that page: there's loads of examples of the CLI doing it, but normally I just edit the file by hand (which is all the CLI does).
busy-toothbrush-9019410/13/2023, 12:33 PM
field with KMS