Open dreinhardt89 opened 2 months ago
Adding some more info. This only seems to occur when we change the provider to point to a new argo cd instance.
Potential upstream reference:
I believe I am having this same issue with my ArgoCD upgrade although I am going to 2.11
Currently we are using Helm Chart: 5.16.13 and I'm trying to upgrade to 6.9.3 (reason for this is a different bug introduced in 6.10 - I think irrelevant to this). This means we're going from App version 2.5 to 2.11, and in this upgrade I am now seeing this permission error when I go to deploy applications.
The errors looked potentially related to grpc
but if I login with the cli I can provision applications using the --grpc-web
flag so I am definitely at a loss as to where to go from here
After upgrading to 2.12 we were denied access to our argocd_repository resources. Reverting back to 2.11 fixed it and doing a terraform state remove then import also fixed it.
We have a lot of apps so upgrading without messing with the state file would be big help
Terraform Version, ArgoCD Provider Version and ArgoCD Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Steps to Reproduce
Expected Behavior
Nothing should change as just the argocd version is updated
Actual Behavior
argocd_repository fails to be read
Community Note