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

You just need to point the provider field of the resources you don’t want to be replaced to the new provider.

the format is `$SOME_STUFF::${providerName}::${providerID}` iirc

ok so what i'll probably need to do is pulumi up targetting just the new providers so they get ids, then reference them in the stack (export - edit - then import)?

there may be a better way to do this, but I’m not aware of any

thanks for the help. trying it out on a small test project first.

<@U020WQKV6AG> <@U01GS450UP5> you can use aliases for this:
<https://www.pulumi.com/blog/cumundi-guest-post/>

The reason this happens is because when you update your pulumi resource with an explicit provider, it updates the urn. If you alias to the old resource, it should keep the same urn

oh that sounds super useful and potentially less error-prone. thanks for that

ok so i finally got round to trying this on Friday and couldn't get it to work. on researching it this morning am i right in thinking the following issue is related to this:
• <https://github.com/pulumi/pulumi/issues/7012>
Think i'm going to have to do the stack export/edit/import workaround

I dont think so? what are you setting as options?