-
Notifications
You must be signed in to change notification settings - Fork 72
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
add support for specified proxy in source GitRepository #565
Conversation
e7add95
to
d0d1f7d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add tests for the new behaviour.
d0d1f7d
to
6416efd
Compare
@makkes the tests for proxy exist in |
6416efd
to
3766025
Compare
@aryan9600 but that doesn't test the wiring of Secret data to actually performing the operation, which should have coverage here. |
3766025
to
cb1a92f
Compare
That's great but this change adds a lot of code around the functionality from pkg/git/gogit that we should test. |
213a0d0
to
96d3827
Compare
96d3827
to
d32d13a
Compare
d32d13a
to
6d91fb7
Compare
Add proxy support for Git operations using the proxy configuration specified in the source GitRepository's `.spec.proxySecretRef`. Refactor the Git client building process to make it more testable. Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Retry reconciliation in `TestImageUpdateAutomationReconciler_deleteBeforeFinalizer` as sometimes it fails with a latest version conflict error. Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
6d91fb7
to
95a7b39
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @aryan9600 🏅
Add support for using the proxy specified in the source GitRepository using its
.spec.proxySecretRef
.also closes #575