-
Notifications
You must be signed in to change notification settings - Fork 263
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
Bug: repocreds do not GitHub App credentials #754
Comments
After doing some more digging, it appears that the following statement is no longer being respected:
I say this because as soon as I update my
Then |
Sorry, I did not mean to close the issue! |
After doing quite a bit of investigation, it appears that the bugs I was finding actually had to do with the fact that I was defining my GitHub app credentials via an ArgoCD credential template. However, likewise, even after switching to a repository set of github credentials, it looks like the legacy repo provider doesn't support loading the GitHub app credentials at all. |
This should have been fixed by #737, which is not yet released. If you feel like it, you could test from a latest image though. |
@jannfis even with the latest image, the error becomes this issue:
|
@abatilo can you try with the latest image now? This should be fixed now. |
@benfuu Thank you so much for looking into this. It looks like image I'm happy to close this and open a different issue if you'd prefer? Here's the new set of logs.
Perhaps there's another pass through required somewhere for gpg settings? I am NOT configuring anything related to commit signing whatsoever. |
It seems gpg params are added to the git client even when disabled by default: argocd-image-updater/ext/git/writer.go Line 31 in 9ad9e4f
|
Describe the bug
Between version v0.12.2 and v0.13.1, it seems like some bug was introduced which is causing authentication failures when trying to write changes back to the git repository.
To Reproduce
I have the following
kind: Application
that works perfectly withv0.12.2
and stops working atv0.13.1
Expected behavior
I would expect
argocd-image-updater
could continue to write commits to thespec.source.repoURL
after doing the upgrade.Additional context
I'm using a GitHub App for authentication as documented here
Version
v0.13.1
Logs
Here are trace level logs:
The text was updated successfully, but these errors were encountered: