If i add a provider to an azure-native stack that's already been deployed before the provider was added Pulumi wants to replace resources instead of just updating them. For a lot of resources in the stack that's fine, but for others, like db's this is not optimal. Is there anything I can do to make Pulumi think these are still the same resources, and all it needs to do is update the provider? The provider was added as we moved some resources in a stack across to a different azure subscription, whilst others (e.g. dns zone) remained in the old subscription.

We do this by manually editing the state

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)?

yes

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

@witty-airport-81009 @prehistoric-kite-30979 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

nice

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

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