-
Notifications
You must be signed in to change notification settings - Fork 244
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
Make occlient a superset of kclient #2643
Make occlient a superset of kclient #2643
Conversation
Signed-off-by: John Collier <John.J.Collier@ibm.com>
Signed-off-by: John Collier <John.J.Collier@ibm.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: John Collier <John.J.Collier@ibm.com>
Signed-off-by: John Collier <John.J.Collier@ibm.com>
/test v4.1-integration-e2e-benchmark |
1 similar comment
/test v4.1-integration-e2e-benchmark |
@johnmcollier: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
What type of PR is this?
What does does this PR do / why we need it:
This is an alternate draft PR to #2626, exploring an alternate approach to handling overlap between occlient and kclient.
Rather than keeping occlient and kclient functions completely separate, this PR adds an instance of kclient to the occlient instance, thus making occlient a superset of kclient. This works out nicely because occlient already has all of the fields that exist in kclient so we can use this as a chance to refactor and reduce some code duplication.
Additionally, this approach prevents us from having to pass in both
occlient
andkclient
instances into the CLI context (and from having to pass in both to functions that require them).As a summary, this PR does the following:
occlient
package to thekclient
package, so that it can be used with both odo "classic" push and odo "devfile" push.kclient
instance to theocclient
objectocclient.kclient
where applicableAll unit tests passing:
Which issue(s) this PR fixes:
#2473 (partially)
How to test changes / Special notes to the reviewer: