Re: [Proposal] Making the Service Broker API less CF-specific
Gwenn Etourneau
HI,
I think this change is important and need to be done, I like the new
context parameters but not sure about the `optional`, I think it's
important to which env. / platform we are talking too.
Thanks,
On Thu, Apr 20, 2017 at 7:38 PM, Matthew McNeeney <mmcneeney(a)pivotal.io>
wrote:
I think this change is important and need to be done, I like the new
context parameters but not sure about the `optional`, I think it's
important to which env. / platform we are talking too.
Thanks,
On Thu, Apr 20, 2017 at 7:38 PM, Matthew McNeeney <mmcneeney(a)pivotal.io>
wrote:
The Open Service Broker API [1] working group have created a proposal [2]
to make the Service Broker API less CF-specific. The proposed changes will
help grow the services community by allowing service broker authors to
create and deliver services to a range of cloud-native platforms (including
Cloud Foundry, OpenShift and Kubernetes).
The key parts of the proposal are:
- Platforms can *optionally* send a new *context *parameter to service
brokers containing platform-specific information (a Cloud Foundry platform
would send the platform name, the organization GUID and the space GUID).
- The existing *required *CF-specific parameters, *organization_guid *and
*space_guid *will be marked as deprecated to be removed from the
specification in a future version.
We'd love to get some feedback from the community on this proposal.
Many thanks,
Matt
-
[1] https://www.openservicebrokerapi.org/
[2] https://github.com/openservicebrokerapi/servicebroker/issues/115