This message was deleted.

sparse-intern-71089

07/28/2021, 9:08 PM

This message was deleted.

chilly-lamp-75954

07/28/2021, 9:09 PM

in particular - I am using that on github resource, but it still seems to be trying to replace resource, instead of ignore the custom provider passed.

little-cartoon-10569

07/28/2021, 9:10 PM

To clarify: you don't mean that the provider is changing properties on your resource; you mean that you are changing the provider on your resource? And you want to leave the resource unchanged?

chilly-lamp-75954

07/28/2021, 9:11 PM

Hi Paul, yes, I’ve started passing

provider

to options and would like that not to impact on the history of resource.

chilly-lamp-75954

07/28/2021, 9:13 PM

actually, the reason why I started doing that is that I cannot use github.token from environment/configuration on my project for unrelated reasons, so I found needing to construct my github provider on the fly after initial resource was created.

little-cartoon-10569

07/28/2021, 9:14 PM

This question has been asked quite a few times. I think someone came up with a way to do it without editing the stack, but I forget how. When I have done it, I've always edited the stack manually.

little-cartoon-10569

07/28/2021, 9:15 PM

Create the new provider, ideally use it at least once. Export the stack. Update all resources that your want to change; they all have a provider property in their opts. Import the stack.

👍 1

little-cartoon-10569

07/28/2021, 9:16 PM

Don't forget to make a backup of your stack 🙂

🤞 1

chilly-lamp-75954

07/28/2021, 9:16 PM

I see, thanks, I’ll dig history too, many thanks! In your experience, did it bubble up the chain when provider configuration changed? (just thinking if I go with manual stack edit for this case if I would need to change it every time my token changes or not)

little-cartoon-10569

07/28/2021, 9:21 PM

No. The change on resources changes a pointer to the provider, not the values within the provider. You should be good to do in-provider work safely any time you need.

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