Nathanael Liechti

@SteveJ-IT your `permission denied` error sounds more like #416 or a related issue. Where as the other ones could be related. I'm assuming you are also using the provider with...

@jpatavahi you're error also sounds familiar to what we experience in our CI env a lot. That is surely related to the argocd-server pod being gone and the provider not...

I think I found an interesting pattern. The `core` mode starts a local Argo CD api-server instance for every resource's CRUD functions and uses this to communicate (and the api-server...

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...

So after rereading the issue a couple of times I think I know what it's about. Sorry for the detail @NGAJean. Let me try to explain with a reproduction example,...

The related PR has been merged and my local tests were successful. Github is currently building a patch release `v7.11.2` that includes the fix. Let me know if that works...

Let me take a look at it...

I can reproduce the issue with the following procedure: ```console kind create cluster --name argocd kubectl create namespace argocd kubectl apply -f https://github.com/argoproj/argo-cd/raw/refs/tags/v2.12.4/manifests/install.yaml -n argocd ssh-keygen -t ed25519 -C "Argo...

Really strange, when I set the private key without "", it seems to work. @Vermyndax can you validate in which format you set the variable for the private key and...

@Vermyndax were you able to check/verify?