-
Notifications
You must be signed in to change notification settings - Fork 105
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(sync): added bearer client for sync #2222
fix(sync): added bearer client for sync #2222
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2222 +/- ##
==========================================
- Coverage 92.89% 92.79% -0.10%
==========================================
Files 165 166 +1
Lines 21582 21760 +178
==========================================
+ Hits 20048 20192 +144
- Misses 956 980 +24
- Partials 578 588 +10 ☔ View full report in Codecov by Sentry. |
94f6d12
to
11a34e5
Compare
ba08f4d
to
24f9536
Compare
9d8e00d
to
a16ecab
Compare
a16ecab
to
61bcdfd
Compare
61bcdfd
to
fa27ac8
Compare
fixed ping function taking too much time closes: project-zot#2213 project-zot#2212 Signed-off-by: Petu Eusebiu <peusebiu@cisco.com>
fa27ac8
to
f4352b9
Compare
This should solve two of your issues, one is periodically sync now should work with your azure instance. Can you test it on your side please? |
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
fixed ping function taking too much time
closes: #2213 #2212
What type of PR is this?
bug
Which issue does this PR fix:
Fixes the sync taking too much time to fallback to serving local cached image, in case the remote is unavailable.
Added bearer auth for http client.
Should also fix multiple unauthorized messages we saw in sync logs when trying to sync referrers.
This is WIP
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:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.