Open WilliamCoffeyTri opened 2 years ago
Expanding on this with a bit of new info- I had used the address format provided by CodeCommit. After adjusting it to mimic the format provided by github instead, ArgoCD seems to find the repository but still fails, reporting a success message for SSH authentication as the error. This is seeming more like an odd quirk of AWS, and potentially how ArgoCD interacts with it.
Attached image demonstrates the issue. It is being run directly from the argocd-server container.
I have an AWS CodeCommit repository which very explicitly does exist, that ArgoCD can't recognize. The appropriate private/public key pair was generated and the public key was provided to an AWS account with access to CodeCommit. As demonstrated above, I can pull from the repository using the key with git. However, attempting to do the same with the argocd CLI returns "Repository does not exist". Notably, if I do not include --insecure-skip-server-verification I will receive an unknown host, even if I use ssh-keyscan to introduce the CodeCommit root url into my known_hosts.
I'm unclear what the nature of this issue is- whether it's a bug with ArgoCD, a quirk of AWS, or just some foolishness on my part. Let me know if there's any additional information I can gather to clarify this issue.