Bug Modification of cluster (should recreate the ressource or allow to override the existing one)

[NGAJean]

Terraform Version, ArgoCD Provider Version and ArgoCD Version

Terraform version: hashicorp/terraform:1.8
ArgoCD provider version: argoproj-labs/argocd v7.1.0
ArgoCD version: v2.12.3+6b9cd82

Affected Resource(s)

• argocd_cluster

Debug Output

Error: failed to update cluster https://xxxxx
rpc error: code = PermissionDenied desc = permission denied

Steps to Reproduce

1. register a first cluster
2. register a new cluster with the same name
3. modification failed

Expected Behavior

Automatically trigger a resource recreation or allow via a parameter like upsert in cli to override the existing one.

Actual Behavior

Modification failed

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

[the-technat]

Hi @NGAJean would you mind sharing an example TF file to reproduce the issue? I cannot imagine what you mean by "register a new cluster with the same name". Is this a second argocd_cluster resource you are adding or something you do via CLI/UI?

[NGAJean]

Hi @the-technat, the usecase is the following.
We are using EKS, sometimes when we change some low level parameters we have to recreate the entire cluster.
The new cluster have the same name than the previous one but with a different endpoint and CA authority.
To update the cluster definition on the argoCD application side with the cli we are able to use the upsert flag to override an existing cluster (the previous one) with the same name even if the spec differs (the new one).
What we expect with this argocd terraform provider is that if the endpoint and/or the ca authority for an existing `argocd_cluster terraform ressource change it trigger a recreation of this terraform ressource instead on failed on the apply command.
Is it more clear now ?