LATEST VERSION: 2.0 - RELEASE NOTES
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 (PCF)

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

For each client application, you must:

  • Update the build file to use the new versions of the Spring Cloud Services client dependencies (see Client Dependencies)

Migrating from 1.3.x

For each client application, you must:

  • Update the build file to use the new versions of the Spring Cloud Services client dependencies (see Client Dependencies)

Migrating from 1.2.x

For each client application, you must:

  • Update the build file to use the new versions of the Spring Cloud Services client dependencies (see Client Dependencies)

Migrating from 1.1.x

For each client application, you must:

  • Update the build file to use the new versions of the Spring Cloud Services client dependencies (see Client Dependencies)

Migrating from 1.0.x

For each client application, you must:

  • Update the build file to use the new versions of the Spring Cloud Services client dependencies (see Client Dependencies)
  • Update the build file to use the Maven BOM dependencies for Spring Boot and Spring Cloud (see Client Dependencies)

For each Circuit Breaker Dashboard service instance, you must:

  • Upgrade the service instance (see Service Instance Upgrades), then unbind, rebind, and restart each of the service instance’s client applications (this is due to a change in how service instance credentials are managed)

Known Issues

See below for known issues in Spring Cloud Services 1.5.x.

  • Version 1.5.6 and prior: Passwords created by Spring Cloud Services do not support changes made to the UAA password policy.
  • Spring Cloud Services releases 1.5.5 and previous are not compatible with PCF Ops Manager 2.2.

1.5.8

Release Date: 21st August 2018

Fixes included in this release:

  • Resolved an issue that could prevent the “Deploy Service Broker” errand of the Spring Cloud Services tile from completing sucessfully in a Cloud Foundry foundation with a large number of spaces.

1.5.7

Release Date: 7th August 2018

Fixes included in this release:

  • Added support for custom password policies configured on Pivotal Application Service.

1.5.6

Release Date: 2nd July 2018

Fixes included in this release:

  • Resolved an incompatibility with PCF Ops Manager 2.2.

1.5.5

Release Date: 18th June 2018

Fixes included in this release:

  • Resolved a Spring Cloud Services service broker incompatibility with MySQL service instances provided by the Azure Open Service Broker for PCF.

1.5.4

Release Date: 7th June 2018

Enhancements included in this release:

  • Service broker requests to the Cloud Foundry API have been optimized to better support large-scale deployments of Spring Cloud Services.

1.5.3

Release Date: 21st May 2018

Enhancements included in this release:

  • Upgrade to Spring Cloud OSS Edgware.SR3 release.

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