-
Notifications
You must be signed in to change notification settings - Fork 34
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
replace methods of the CRTRestClient with the cached client #462
replace methods of the CRTRestClient with the cached client #462
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #462 +/- ##
==========================================
+ Coverage 79.46% 81.17% +1.71%
==========================================
Files 42 42
Lines 2727 2630 -97
==========================================
- Hits 2167 2135 -32
+ Misses 471 407 -64
+ Partials 89 88 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ 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.
+68 -221
I like this ratio for these reg-service refactoring PRs :)
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.
Nice cleanup 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexeykazakov, MatousJobanek, mfrancisc, xcoulon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Quality Gate passedIssues Measures |
e15d7cc
into
codeready-toolchain:master
This is a follow-up of #461
It replaces the methods of the custom CRTRestClient with the cached client that is already used instead of the custom shared informers. With this, we will use only one client in both proxy and reg-service which is cached and optimized.
I'm changing the implementation of the methods only to minimize the scope of the changes in the PR.
Changes in unit-tests and removal of the extra layers will be addressed in many following (and most likely huge) PRs 😬
KUBESAW-133