Skip to content
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.

Sign up for GitHub

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

Jump to bottom

We should move to using the openshift client-go #590

Closed
shawn-hurley opened this issue Dec 13, 2017 · 2 comments
Closed

We should move to using the openshift client-go #590

shawn-hurley opened this issue Dec 13, 2017 · 2 comments
Labels
3.11 | release-1.3 Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3 feature

Comments

@shawn-hurley
Copy link
Contributor

Feature: Use Openshift Client Go and Openshift API

The [openshift client-go] and [api] should be used instead of our [openshift client] that we have been using. This will require a change to our copied modules here as well, but should then easily changed.

This will give us access to all of the openshift APIs without building our own rest clients now.
@shawn-hurley shawn-hurley mentioned this issue Dec 19, 2017
Merged
@rthallisey rthallisey added enhancement 3.10 | release-1.2 Kubernetes 1.10 | Openshift 3.10 | Broker release-1.2 labels Jan 9, 2018
@rthallisey rthallisey added 3.11 | release-1.3 Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3 and removed 3.10 | release-1.2 Kubernetes 1.10 | Openshift 3.10 | Broker release-1.2 labels Mar 6, 2018
@shawn-hurley
Copy link
Contributor Author

This should be closed once automationbroker/bundle-lib#105 is merged

@jmrodri
Copy link
Contributor

jmrodri commented Jul 23, 2018

Fixed by PR automationbroker/bundle-lib#105

@jmrodri jmrodri closed this as completed Jul 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.11 | release-1.3 Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3 feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jmrodri @shawn-hurley @rthallisey