New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git artifact fetch of reference fails due to missing credentials #2343
Comments
It is simply the case that we do not support authentication for Git. I think we should remove the go-git library and use Git directly. @jessesuen @sarabala1979 reason for using go-git here? |
I have been looking at an example very similar to the above which currently exists within the argo repository and it talks about authenticating to a private git repository. https://github.com/argoproj/argo/blob/master/examples/input-artifact-git.yaml Is this really not possible? how else are we supposed to do CI on a private repository? If it's not possible what is the above actually an example of? |
Maybe related: #3246 |
I'm the same person, my use case is slightly different and shows it being supported in the example I provided so I opened a new ticket :) |
v2.10 |
Checklist:
What happened:
I tried to checkout a gerrit change reference, using git artifacts. It failed due to the fetch didn't use authentication.
What you expected to happen:
The repo is cloned and the change is fetched and checked out.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
To verify the setup I tried a clone and checkout a revision that exists, like a branch, and then it works, so it's the
fetch
that fails.It can also be seen in artifacts/git.go that
Auth
is missing fromFetchOptions
(https://github.com/argoproj/argo/blob/master/workflow/artifacts/git/git.go#L106).Environment:
Other debugging information (if applicable):
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: