Implement support for `move` from unversioned to versioned resource types.

[peak-stephen]

Description

it's been possible for providers to moving an existing resource to a new resource type since Terraform 1.8 (release notes).

The recent deprecation of all unversioned resources would be a lot simpler to handle if this provider supported that. In my case the project uses terraform HCP which does not allow for the terraform import command, so I either have to live with endless deprecation warnings, or do some very dangerous state-file editing.

Potential Terraform Configuration

moved {
  from = kubernetes_service.whatever
  to = kubernetes_service_v1.whatever
}

References

1. Terraform 1.8 release notes
2. Reference for MoveState in terraform plugin development docs: https://developer.hashicorp.com/terraform/plugin/framework/resources/state-move

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[krische]

In my opinion, this is a must-have if the non-versioned data and resource items are going to be deprecated.

[gionn]

Same of #2812

[gss2002]

This is beyond necessary the fact that this is non-existant is a HUGE miss by this provider

[Shlomit-B]

Hi, I'd like to work on this if that's OK. I'm planning to start by migrating just kubernetes_namespace_v1 to the Framework provider and implement ResourceWithMoveState there to accept state from kubernetes_namespace, using the existing ValidatingAdmissionPolicy Framework resource as a template. The unversioned kubernetes_namespace would stay in SDK v2.
Does this approach look reasonable to the maintainers before I start implementing?