-
Notifications
You must be signed in to change notification settings - Fork 104
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
fix: enable TLS based on URL scheme for sync extension #2747
Conversation
@evanebb thanks for your PR. Started a CI run, let's see what happens. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2747 +/- ##
=======================================
Coverage 92.07% 92.08%
=======================================
Files 169 169
Lines 30052 30054 +2
=======================================
+ Hits 27671 27674 +3
+ Misses 1762 1760 -2
- Partials 619 620 +1 ☔ View full report in Codecov by Sentry. |
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. @eusebiu-constantin-petu-dbk, can you please take a look too?
and push again. This should resolve the DCO failure. The PR looks good btw. |
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 and thank you for fixing it.
Signed-off-by: evanebb <78433178+evanebb@users.noreply.github.com>
653b420
to
d441f35
Compare
Thank you! I amended the commit to add the DCO and force pushed it, so let's see if the workflow is happy now. |
What type of PR is this?
bug
Which issue does this PR fix:
#2557
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Note: I haven't managed to run a full
make
yet, my Mac seems to not play nice withgolangci-lint
and starts leaking memory heavily :)I spun up a local instance of zot (with locally built images) and an 'upstream' repository with HTTPS enabled using a self-signed certificate with the following
docker-compose.yml
:And the corresponding
config.json
:I pushed a test image (
ubuntu:latest
) into the upstream registry with:And then tried pulling it through the zot instance on my local machine with:
When using a version of the zot image that doesn't have the fix applied, this results in the following error:
The corresponding zot logs show the same thing:
If I build a local image with the fix and use that one, it seems to work fine:
Once again, the corresponding zot logs:
Automation added to e2e:
I haven't added anything, if it is desired for this change please let me know.
Will this break upgrades or downgrades?
Not as far as I know.
Does this PR introduce any user-facing change?:
No.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.