This message was deleted.

What do you mean you lost it? Was it deleted? When using the local backend Terraform makes a backup state, do you have any of those?

State file is complectly losed and Please guide how can I know the existing resource list to import the resource to rebuild the state file

Welp, there isn't a way to know which resources your Terraform used to manage so you are going to have to decide which resources in your cloud provider you want to manage and how they relate to your config.

I was deployed RKE2 downstream cluster through terraform and I have the same workspace.

ok, you are saying that the one state file (that was lost) was serving multiple workspaces (dev, sit, uat, and prod), and was deploying identical environments, so when you lost your state file you now have a jumble of identical resources that was kept separate by Terraform workspace, right?

All the environment has separate workspace with own state file Now I lost uat and Prod environment state file only, I have the dev,sit state file and all terraform config are identical

If you are deploying clusters through Rancher then you only need to find the Rancher resources and import them. These would be a rancher2_cluster_v2 resource.

Yes, we deployed through Rancher custom downstream cluster, how to know existing resources list for the import?

Just import the cluster resource

Hi Matt, I have tried to import the rancher2_cluster_v2 resource and getting below error.

Is the downstream cluster rke1 or rke2?

It's RKE2

Does you cluster have a name in Rancher?

Yes, we have named it dev-cluster, sit-cluster and prd-cluster

When you view the yaml version of the cluster in the Rancher UI does it have a Status.Name ?

Please find the below screenshot of status and name through Rancher UI

hmm, welp, sounds like Terraform is having trouble reading it. Try setting TF_LOG to TRACE and see if you can find the API call and responses.

Hi Matt, I successfully imported the downstream cluster resources, and the Terraform state file has been generated and stored remotely. the error which I encountered during import before "Error: Setting cluster V2 legacy data: cluster_v1 id is empty" Root Cause: This issue occurred due to an incorrect Cluster ID being provided during the import process. Solution: Ensure that the correct Cluster ID is used when running the Terraform import command. The correct format is:

terraform import <resource_type>.<resource_name> <resource_id>

Example: terraform import rancher2_cluster_v2.cluster fleet-default/prd-cluster

Great News!!