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

<@U036QTANYG4> because you're changing the URN. you can use to point to the old resource urn and stop the deletion behaviour:

<https://www.pulumi.com/docs/intro/concepts/resources/options/aliases/>

once the urn has been updated pulumi knows the two resources are related, and reconciles them

thanks a lot.
After your advice, I fixed the issue by adding `aliases=['old-urn']` .
It would be great to add this to `parent` ResourceOptions documentation page. Because this behaviour looks pretty confusing for a new user.

It is there. 3rd last paragraph:
&gt; aliases: Aliases applied to a parent are applied to all child resources, so that changing the type of a parent resource correctly changes the qualified type of a child resource, and changing the name of a parent resource correctly changes the name prefix of child resources.

Wording is reasonably indecipherable though. Could be simplified.