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

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. 

is there something that will be included by default on the new resource? am i better off waiting?

or perhaps i could manually edit the state file so they match?

not keen on having long-lived aliases all over and replacing the resources would tear down all our clusters

I just ran a test with the intention of trying to patch my state file - it ran fine without any changes required!