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

also, will this update the secrets in the config file if I am in the right folder or do I have to deal with that manually?

It should be instant - within seconds and it will change the confit AND the state

Ok, will have to try tomorrow again then. 

What I’m trying to do is moving the state from one blob to another and also change the secrets provider. My assumption is that it should work if I first copy the state and then just do change secret provider. Correct? (Don’t ask me why I’m doing this :) )

I think you should carry this out as separate operations

Exactly what I’m planning to do, change provider, make sure it works, then move state to new storage. 

When I run it I get:

&gt; error: secrets (code=InvalidArgument): keyvault.BaseClient#Decrypt: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadParameter" Message="The parameter is incorrect.\r\n"
It does change the provider in the yaml file, but that is all that is changed.

if you were using Azure, it was hanging for me forever until I set ENV variable to true

$env:AZURE_KEYVAULT_AUTH_VIA_CLI = $true

I have that. I also manage to create secrets against both keyvaults. I wonder if I need some more permissions. 

It will require decryting the secrets <@UTR14TXEY>

It needs to decrypt to be able to re-encrypt

I have those, otherwise I guess I wouldn't be able to create at all.

<@UP8AFFF41>, which OS did you run it from?

Have an issue for it here by the way. <https://github.com/pulumi/pulumi/issues/5835>