LATEST VERSION: 1.5 - CHANGELOG
Spring Cloud Services v1.5

Release Notes for Spring Cloud® Services on Pivotal Cloud Foundry

Release notes for Spring Cloud Services for Pivotal Cloud Foundry

Important: The service broker applications in Spring Cloud Services 1.5 use the system org’s system domain, and expect this domain to be a shared domain (the default setting). If you make the system org’s system domain private, Spring Cloud Services 1.5 will fail to push applications to the system org.

Migrating from 1.4.x

If you are upgrading from a 1.4.x release of Spring Cloud Services, no changes are required for client applications or Spring Cloud Services service instances.

Migrating from 1.3.x

If you are upgrading from a 1.3.x release of Spring Cloud Services, no changes are required for client applications or Spring Cloud Services service instances.

Migrating from 1.2.x

If you are upgrading from a 1.2.x release of Spring Cloud Services, no changes are required for client applications or Spring Cloud Services service instances.

Migrating from 1.1.x

If you are upgrading from a 1.1.x release of Spring Cloud Services, no changes are required for client applications or Spring Cloud Services service instances.

Migrating from 1.0.x

The Spring Cloud Services client dependencies were restructured in 1.1.0. In 1.5.x, they are based on Spring Cloud Camden. To ensure compatibility of your client applications with Spring Cloud Services 1.5.x service instances, you must update your client applications to include the current dependencies and the Spring Boot and Spring Cloud Maven BOM dependencies. For information about upgrading Spring Cloud Services service instances after upgrading the Spring Cloud Services product, see the Service Instance Upgrades topic. For complete information about the current Spring Cloud Services client dependencies, see Client Dependencies.

After upgrading a 1.0.x Circuit Breaker Dashboard service instance to a 1.5.x version, you must unbind, rebind, and restart any client applications which were bound to the instance. This is due to a change in how service instance credentials are managed.

1.5.2

Release Date: 26th February 2018

Enhancements included in this release:

  • The stemcell has been updated to 3468. This resolves the following issues:

1.5.1

Release Date: 29th January 2018

Enhancements included in this release:

  • Resolved an issue with the Spring Cloud Services support for beta CredHub service broker integration. This issue occurred if the Spring Cloud Services service broker received an error from CredHub when attempting to delete credentials: the binding or instance deletion operation would fail and leave the service instance in a broken state. The Spring Cloud Services broker now handles this situation by not failing due to a failed CredHub binding deletion attempt.

1.5.0

Release Date: 22nd December 2017

Enhancements included in this release:

  • The Spring Cloud Services service broker and worker apps now can use the Runtime CredHub to store service instance credentials. Operators can enable use of CredHub in the Spring Cloud Services tile settings. For more information, see the Secure Service Instance Credentials with CredHub section of the Tile Configuration topic.
  • The dependent services used by the Spring Cloud Services service broker are now configurable during installation by operators. Operators can specify alternative services and service plans for the service broker’s persistence store (the default is MySQL for PCF) and message bus (the default is RabbitMQ for PCF) services. For more information, see the Installation topic.

    Note: The new settings for persistence store and message bus services affect the service broker’s dependent services only (they do not affect services used by service instances).

  • The Config Server’s composite backend now accepts the pattern and searchPaths properties for a Git backend within a composite. For more information, see the Composite Backends topic.
  • The Spring Cloud Services service broker has been upgraded to Spring Boot 1.5.7 and Spring Cloud Edgware.RELEASE.
Create a pull request or raise an issue on the source for this page in GitHub