spring-cloud-open-service-broker
spring-cloud-open-service-broker copied to clipboard
Support OSB API 2.16
Release notes: https://github.com/openservicebrokerapi/servicebroker/blob/master/release-notes.md#v216
- [x] Add guidance for remembering the state of service instance and service binding operations (no code changes required)
- [x] Add guidance to handle 500 errors from Service Instance update (no code changes required)
- [x] Add guidance to handle requests with invalid data (no code changes required)
- [ ] Allow Service Brokers to indicate if a Service Instance is still usable after a failed update or deprovisioning and if an update can be repeated (#353)
- [x] Specify that Platforms SHOULD NOT reuse IDs (no code changes required)
- [x] Allow the platform to supply Service ID and Plan ID as hints when retrieving a service binding or a service instance (#287)
- [ ] Add CF and K8s annotations to the profile document
- [ ] Add support for ETag and If-Modified-Since headers
- [ ] Clarify the response code when Platform does not provide the required API version header
- [x] Service Instances can be labelled with information defined by the Service Broker (#311)
- [x] Add expiration date and time for bindings (#335)
@royclarkson - could you please suggest the timeline to enable support for OSBv2.16 with latest version of Spring Boot 2.7.x? I can see in the readme that its under development. Thanks
We would need this feature for a Siemens project. So we would be very interested for an update, ...
@kamalsethiya @StefanREbertsch are there OSB 2.16 features that you need that are currently not supported within the current release? Many of the outstanding items here are guidance and don't require code changes.
@royclarkson - I cross verified from the features point of view and seems like all the needed things are already implemented related to v2.16 in the current release.
We asked this question because in the read me its mentioned that v2.16 is still under development:

Also, value for constant BrokerApiVersion.API_VERSION_CURRENT is 2.15. Please suggest what's the plan to update its value to 2.16.
Thank you Ray. We will go forward and see if something else is missing. See the last request from Kamal.
@kamalsethiya added #358 to update that version in the next release. Thanks.
Thanks @royclarkson.
All outstanding OSB API 2.16 issues have been addressed