Not quite sure why it would be trying to delete those resources on

update

They have the exact same resource names in the Pulumi program, the stack and in Azure

All I did was: 1. Migrate the code to the new native provider 2. Import these 3 resources 3. Attempt an

update

We do not use auto-naming of resources btw, instead we include the stack name in the resource names and specify them explicitly on all resources.

Any idea what’s going on anyone, and how I can get out of it?

It seems I somehow ended up with duplicate resources in the stack:

So it’s trying to both replace and delete them?

Not sure how this could happen?

Do I need to do the import before I migrate the code?

It completed successfully for each of them.

Changing no properties, just migrating to AzureNative

After that, imported these 3 resources, no problem

Then on

update

Pulumi decides they need to be replaced

Because of differences between “westeurope” and “WestEurope” it seems?

And in addition, the old resources are still in the stack also, and those are show for deletion in the preview

And they have the same name!

Manually

For the resource group for example, this only meant changing the namespace import basically.

Maybe I should clarify, here are the steps I performed: • Change the code from classic to native, keeping the same resource names and all other properties • Run

pulumi import

on these 3 resources - successfully • Run

pulumi up

• Preview fails because Pulumi thinks it needs to replace these 3 resources, but they are marked as protected by the import • Manually removed the protection from the stack using

stack export

and

stack import

to be able to preview • Run

pulumi preview

which shows my second screenshot above

I get it

I’ll try it