This message was deleted.

If you just replace directly, yes, new resources will be created. You should be able to use the new

aliases

feature to alias the resources to the old names/types they had in the older provider. Assuming the resources are sufficiently “the same” in old and new providers, this should allow an update that does not replace. You can add

aliases: { type: “theoldtypetokenfortherwource” }

to the resource options and then check that a preview does not suggest a replacement. Docs on this coming very soon.

ah eek