1.0.1.RELEASE

This release brings support for the Cloud Foundry Service Broker API from version v2.8 to v2.11. This includes the addition of the following API features:

• Requests to the last_operation service broker API endpoint include two new fields - serviceDefinitionId and planId.
• Responses from asynchronous create, update, and delete requests may include an operation field. The value of this field is sent back to the broker by Cloud Foundry in each call to the last_operation endpoint.
• Responses from create requests may include a volumeMounts field to indicate that the service provides network storage mounts to the application container.
• Plan definitions in catalog metadata can now include a bindable field. This allows a service provided by a broker to have both bindable and non-bindable plans. This field is optional; if not provided, the bindable field in the service definition applies to all plans of the service.

In addition to these broker API enhancements, features were added to support registering a service broker to multiple Cloud Foundry instances.

• If a unique ID is provided as part of the URL when a broker registers to Cloud Foundry, a cfInstanceId field in every request object is populated with the value of this ID.
• An apiInfoLocation in every request object is populated with the value of the X-Api-Info-Location HTTP header that Cloud Foundry passes to each call to the service broker.

This release is the result of feedback and contributions from several community members. You can view the full list of changes on GitHub.