This message was deleted.

sparse-intern-71089

06/21/2021, 2:50 PM

This message was deleted.

brave-planet-10645

06/21/2021, 2:54 PM

Yes. Instructions are here: https://www.pulumi.com/docs/intro/concepts/state/#logging-into-the-google-cloud-storage-backend

lemon-monkey-228

06/21/2021, 3:03 PM

I’ve logged in okay, but I still have a

Pulumi.x.yaml

locally

lemon-monkey-228

06/21/2021, 3:03 PM

Let me double check I’ve done it right. I have used state tracking in another project but I started this one off without any tracking (local and blowing away the state)

lemon-monkey-228

06/21/2021, 3:03 PM

So I wonder if there’s something badly configured

lemon-monkey-228

06/21/2021, 3:06 PM

Sorry, when I say config, I might mean ‘secrets provider’ (

pulumi config get …

)

lemon-monkey-228

06/21/2021, 3:06 PM

I’ll re-read the docs, including https://www.pulumi.com/docs/intro/concepts/config/#changing-the-secrets-provider-for-a-stack and see if that’s what I need

lemon-monkey-228

06/21/2021, 3:06 PM

thanks

great-sunset-355

06/21/2021, 3:31 PM

I tested migration from hosted to self-managed, I changed a secret service to

passphrase

and then

pulumi login s3://

and

p .. stack import

The reason I needed to change secret service was that exported state still pointed to pulumi secret service and that did not allow me to import it

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