Problems with resource mv in terraform, moving to new naming convention for workers resources

[EdsonLuisVieira]

Confirmation

• This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
• I have searched the issue tracker and my issue isn't already found.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform v1.5.5
on darwin_amd64
+ provider registry.terraform.io/cloudflare/cloudflare v4.39.0

Affected resource(s)

cloudflare_worker_route --> cloudflare_workers_route
cloudflare_worker_script --> cloudflare_workers_script

Terraform configuration files

When changing the resources that are going to be deprecated from version 4.38.0 to 4.39.0 I see the output that the resources are going to be recreated, something that I don't want to happen, so I try to make the move and get an error that this is not possible, I would like an option where to update to the new version it is not necessary to delete the existing resources.

Link to debug output

https://gist.github.com/EdsonLuisVieira/db06077d60a1910ea1c1722a15c579e5

Panic output

No response

Expected output

moved successful or the name change does not generate a delete recreate

Actual output

│ Error: Invalid state move request
│
│ Cannot move module.cloudflare_resources["0"].cloudflare_worker_route.route
│ to module.cloudflare_resources["0"].cloudflare_workers_route.route:
│ resource types don't match.

Steps to reproduce

Test change version and resource name

1. change version 4.38.0 to 4.39.0
2. update resources name cloudflare_worker_script to cloudflare_workers_script and cloudflare_worker_route to cloudflare_workers_route
3. output show destroy and recreate

Test move

1. change version 4.38.0 to 4.39.0
2. update resources name cloudflare_worker_script to cloudflare_workers_script and cloudflare_worker_route to cloudflare_workers_route
3. move resources
   4.terragrunt state mv 'module.cloudflare_resources["0"].cloudflare_worker_route.route[0]' 'module.cloudflare_resources["0"].cloudflare_workers_route.route[0]'

Additional factoids

No response

References

No response

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

[peikk0]

You need to remove and import them back instead:

removed {
  from = module.cloudflare_resources["0"].cloudflare_worker_route.route
  lifecycle { destroy = false }
}

import {
 id = "<account-id>/<route-id>"
 to = module.cloudflare_resources["0"].cloudflare_workers_route.route[0]
}

[github-actions]

Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the lifecycle/stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.

[mabed-fr]

Hello,

Route workers are not available in v5?

Regards