-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Authentication Failure with Git Artifacts Inputs #8380
Comments
Do not run |
I don't have enough information it this PR to reproduce the issue. I know you cannot share your PAT. Instead, what about spending 30m on a Zoom? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
I'm getting this with |
The bug is in this line of code: argo-workflows/workflow/artifacts/git/git.go Line 155 in 16fef4e
It is missing auth. It should look more like this: argo-workflows/workflow/artifacts/git/git.go Line 137 in 16fef4e
@mgoodness would you like to submit a PR to fix? |
Woot! Sure, PR incoming. |
I'm still getting the error on argo-workflows master branch from commit hash 61211f9d. Plus
My workflow is a modified version from input-artifact-git.yaml
|
I also get the same error ,the workflow
|
Same here
|
Checklist
Summary
What happened/what you expected to happen?
Using git artifacts as input throws 'authentication error' in latest version. This started happening last week with local setup that i was testing. The solution was to move to the comunity helm chart (i wasn't able to easily bump down the controller version without additional weird errors) and forcing controller to version 'v3.3.1' instead of latest.
During the whole process nothing was changed with PAT or it's access to the repo. The same PAT used (and which worked) and te beginning, stopped working and then worked again after the downgrade to older container version.
What version are you running?
I'm runing the quick postgress example in the docs. Kubernetes v1.19.16
Diagnostics
Please let me know what other details i can provide ir order to allow for reproducibility.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: