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

After upgrading the node dependency `@pulumi/google-native` all of the DNS records I created will be 'replaced' with identical records with a new `urn`. I predict that this could cause disruptions in our DNS. Any ideas on how to avoid the replacement while still being able to upgrade the dependency?

you can use an alias <@U040JJNCMK6>
<https://www.pulumi.com/docs/intro/concepts/resources/options/aliases/>
<https://www.pulumi.com/blog/cumundi-guest-post/>

maybe another option is `pulumi up --target &lt;urn of the new provider&gt;` this can update only the provider field without touching the resource I always find aliases too fiddly