Skip to content
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.

Migrate to 1.8 apimachinery #111

Closed
ash2k opened this issue Jul 28, 2017 · 3 comments
Closed

Migrate to 1.8 apimachinery #111

ash2k opened this issue Jul 28, 2017 · 3 comments

Comments

@ash2k
Copy link
Contributor

ash2k commented Jul 28, 2017

Blocked by Service Catalog using 1.7 apimachinery.
@ash2k ash2k added the blocked label Jul 28, 2017
@ash2k ash2k mentioned this issue Jul 28, 2017
Closed
@nilebox
Copy link
Contributor

nilebox commented Jul 28, 2017

but API machinery 1.8 is not released yet :)
I get that you meant migrating onto master, just to clarify there is nothing to do on the Service Catalog side yet, we'll have to wait until apimachinery 1.8 is released.

@ash2k
Copy link
Contributor Author

ash2k commented Jul 28, 2017

I meant 1.8 when it comes out.
Stuff in apimachinery master is very different to 1.7 branch. Will not work with todays Service Catalog.

@ash2k ash2k mentioned this issue Aug 3, 2017
Closed
@ash2k ash2k mentioned this issue Oct 6, 2017
Closed
@ash2k ash2k removed the blocked label Oct 29, 2017
@ash2k
Copy link
Contributor Author

ash2k commented Oct 29, 2017

Was done in #143 and #144.

@ash2k ash2k closed this as completed Oct 29, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ash2k @nilebox