Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Add support for OSB parameter schemas #822

Merged
merged 3 commits into from
May 31, 2017

Conversation

pmorie
Copy link
Contributor

@pmorie pmorie commented May 9, 2017

Closes #490.

I'm posting this early to see how people feel about the changes to our API; I'll finish the rest when I have cause to believe I won't have to re-do the API changes.

Believe it or not I have gone through a couple iterations before posting this that I didn't like.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label May 9, 2017
@arschles
Copy link
Contributor

arschles commented May 9, 2017

@pmorie changes look ok, but I'd like to see what the controller does with these, so I have a bigger picture. Ping me when you want another review

@pmorie
Copy link
Contributor Author

pmorie commented May 9, 2017

@arschles the controller will do nothing except transform them from the appropriate buckets in the OSB API. These are basically there for people to build UIs around at this point; we can just treat them like blobs.

@pmorie pmorie added this to the 0.1.0 milestone May 15, 2017
@pmorie pmorie force-pushed the parameter-schema branch from fba87ee to 86fae52 Compare May 18, 2017 17:59
@pmorie
Copy link
Contributor Author

pmorie commented May 18, 2017

Still needs:

  • godoc
  • test coverage
  • control flags?

@pmorie pmorie changed the title WIP: add support for OSB parameter schemas WIP: dd support for OSB parameter schemas May 18, 2017
@pmorie pmorie changed the title WIP: dd support for OSB parameter schemas WIP: Add support for OSB parameter schemas May 18, 2017
@pmorie pmorie force-pushed the parameter-schema branch from 512bd1a to 647cf73 Compare May 18, 2017 19:03
@vaikas
Copy link
Contributor

vaikas commented May 19, 2017

As per discussions in the Open Service Broker F2F the proposal being investigated is that the schemas are going to be on the ServiceInstance/ServiceBinding, and not below that in separate methods (like Create / Update, etc.) So, let's hold off on this a little bit.

@pmorie
Copy link
Contributor Author

pmorie commented May 20, 2017

@vaikas-google

As per discussions in the Open Service Broker F2F the proposal being investigated is that the schemas are going to be on the ServiceInstance/ServiceBinding, and not below that in separate methods (like Create / Update, etc.) So, let's hold off on this a little bit.

This implements what is in the proposal here: openservicebrokerapi/servicebroker#165 - did something change during the week?

@pmorie pmorie force-pushed the parameter-schema branch from 2b6885f to aaac418 Compare May 27, 2017 18:39
@pmorie
Copy link
Contributor Author

pmorie commented May 27, 2017

I have a business need to get something in to carry schema information ASAP, so unless the proposal has been redrafted, I would like for this to be in the next release.

@pmorie
Copy link
Contributor Author

pmorie commented May 27, 2017

It looks based on this comment like Matt thinks the proposal should stay the way it is: openservicebrokerapi/servicebroker#165 (comment)

@pmorie pmorie changed the title WIP: Add support for OSB parameter schemas Add support for OSB parameter schemas May 27, 2017
@pmorie pmorie modified the milestones: 0.0.9, 0.1.0 May 27, 2017
@jpeeler jpeeler added the LGTM1 label May 30, 2017
Instance Schema `json:"instance"`
Binding Schema `json:"binding"`
ServiceInstances *Schema `json:"service_instances,omitempty"`
ServiceBindings *Schema `json:"service_bindings,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this changes the wire protocol for communicating with brokers, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It changes the application-layer messages, but they were not correct in terms of the actual proposed change to begin with. They are correct after this PR.

@arschles arschles added the LGTM2 label May 30, 2017
@vaikas
Copy link
Contributor

vaikas commented May 30, 2017

No tests?

@pmorie
Copy link
Contributor Author

pmorie commented May 30, 2017

My bad - this has been pending for long enough I had forgotten that I had a couple tests to add.

@pmorie pmorie force-pushed the parameter-schema branch from 25d45cf to 58e9f2a Compare May 31, 2017 18:40
@vaikas vaikas added the LGTM3 label May 31, 2017
@vaikas vaikas merged commit 97d278a into kubernetes-retired:master May 31, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
broker-api-spec-alpha cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. LGTM1 LGTM2 LGTM3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants