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.

Pulumi Community

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

I’ve logged in okay, but I still have a `Pulumi.x.yaml` locally

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)

So I wonder if there’s something badly configured

Sorry, when I say config, I might mean ‘secrets provider’
(`pulumi config get …`)

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

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