Hello. Any clue why `rancher2_cluster_sync.cluster_sync: make destruction complete after 0s? I need it to wait till real cluster is removed from cloud in my case azure aks. Otherwise after sync completed the terraform remove in my case a cloud_credential then probably this lead to race condition where rancher cluster is removed from rancher ui but stay intact on aks side.

I don't think Cluster Sync can actually wait for a destruction, it's a dummy resource that seems to only know how to watch for active states in the API. I know for us we've gone to using old fashioned time_sleep's in terraform when cluster_sync wasn't enough