Provider has renamed resource, least disruptive way to handle?

Terraform
1

A provider we use has renamed resources in their latest version. They did do this at a major release, and tagged it as a breaking change in the docs. However, they never marked the old one as deprecated, nor have a version where both the old and the new are in existence, so I cannot handle this as I usually would (import the existing resources into the new naming).

As far as I can tell, the two ways to handle this are:

  1. delete all of the resource instances via code with the old version, then recreate them new with the new version, or
  2. delete the statefile and then import into the new naming via IDs.

Obviously these will both have potential disruption and risk (and I’m not even sure if 2 is doable, my suspicion is that the resources won’t support imports since a lot of theirs don’t, and these don’t mention it being available in the docs), so I’m trying to figure out if there’s any other option that I’m missing. (Other than go to a vendor that follows best practices for their provider, but sadly we’re actually facing this with two different vendors right now, one quite large/prevalent, so…)

2

Have you already looked into the moved block?

Although I think it’s more intended for resource naming/path changes, I don’t see why it couldn’t be used here unless it results in a destroy/create in the plan anyway.

3

The moved block needs to be able to find the original in the state though, and since there’s no version of the provider that has the old resource name/definition that can also has and so can create the new, it doesn’t work.