2.0.0.RELEASE

The 2.0.0 release of Spring Cloud Open Service Broker is now generally available. This release includes a minor update to Spring Boot 2.0.3.RELEASE. Thanks to everyone in the community who has offered feedback and submitted issues to help improve this project.

2.0.0.RC2

The following issues were fixed in this release:

• Upgrade to Spring Boot 2.0.2.RELEASE
• Move all exception handling to a ControllerAdvice class to allow for custom exception handling
• Remove dependency on spring-boot-starter-security
• Remove WebFlux starter and autoconfiguration

You can view the full list of changes on GitHub.

1.0.3.RELEASE

The following issues were fixed in this release:

• Prevent remote code execution when mapping request parameters to a Java object.
• Make the plan_id field optional for an update operation (via artkoshelev).

You can view the full list of changes on GitHub.

2.0.0.RC1

This release is expected to be the last release before 2.0.0.RELEASE.

• Changed the artifact ID of the Spring Boot starter artifacts from spring-cloud-open-service-broker-starter-web[mvc|flux] to spring-cloud-starter-open-service-broker-web[mvc|flux] for consistency with other Spring Boot and Spring Cloud projects.
• Added the ability to set the support API version as a property.
• Updated dependencies to be compatible with Spring Boot 2.0.1 and Spring Framework 5.0.5.

2.0.0.M2

This milestone adds more polish and improvements as we continue toward a release candidate.

• Update JavaDoc, reference docs, some more JavaDoc, and more reference docs
• Rename the spring-cloud-open-service-broker artifact to spring-cloud-open-service-broker-core
• Add support for externalized configuration of the Catalog in YAML or Java properties.
• Add support to disable API version checking via a configuration property
• Improve exception handling and logging

2.0.0.M1

This is the initial milestone release of the rearchitected Spring Cloud Open Service Broker project. The project has been renamed from Spring Cloud CF Service Broker.

• Requires Java 8, Spring Framework 5, and Spring Boot 2
• Supports inclusion in either a Spring MVC or a Spring WebFlux application
• Provides improved Spring Boot auto-configuration

1.0.2.RELEASE

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

• Request body for provisioning and updating a service instance and creating a service binding include a context field.
• Catalog responses can include a schemas field.
• Any originating identity HTTP header value is captured and provided to all requests.

In addition to these broker API enhancements, the following features were added:

• Arbitrary fields in a bind resource object will be provided in requests to create a service binding.

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

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.

1.0.0.RELEASE

https://spring.io/blog/2016/06/07/introducing-spring-cloud-cloud-foundry-service-broker

v1.0.0.RC3

[artifactory-release] Release version 1.0.0.RC3