👋 Quick Question on rancher2_cluster_sync usage I’m using the rancher2_cluster_sync resource to wait for an RKE2 cluster(created using terraform) to become active. I’m pulling cluster info using data.rancher2_cluster_v2 or rancher2_cluster_v2, and passing .id to cluster_id, which returns something like:

fleet-default/dev05c

However, terraform apply fails with a timeout error:

Error: Timeout waiting for cluster ID fleet-default/dev05c

I noticed that data.rancher2_cluster_v2.cluster.cluster_v1_id gives the internal Rancher ID (c-m-xxxxxxx), and when I use that instead, the sync works as expected. 💡 So it seems rancher2_cluster_sync.cluster_id expects the internal Rancher ID (c-m-xxxxx) — not the namespaced ID (fleet-default/xxxx). ✅ Can anyone confirm if this is the intended usage?

cc @bumpy-tomato-36167

I forwarded this one to the #C07M052K9D0 channel. Just FYI that is where to get better and quicker responses for Terraform related questions. https://rancher-users.slack.com/archives/C07M052K9D0/p1752630204872339