LATEST VERSION: 1.3 - CHANGELOG
Spring Cloud Services v1.3

Release Notes for Spring Cloud® Services on Pivotal Cloud Foundry

Release notes for Spring Cloud Services for Pivotal Cloud Foundry

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.3.x, they are based on Spring Cloud Camden. To ensure compatibility of your client applications with Spring Cloud Services 1.3.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.3.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.3.8

Release Date: 30th November 2017

Enhancements included in this release:

  • The previous release used an incorrect version of the stemcell. This release corrects that.

1.3.7

Release Date: 2nd November 2017

Enhancements included in this release:

  • The stemcell has been updated to the 3445 line of floating stemcells.

1.3.6

Release Date: 11th July 2017

Enhancements included in this release:

  • The Spring Cloud Services service broker now can use a private domain to deploy service instance backing applications when no shared domains are available in the Elastic Runtime deployment.

1.3.5

Release Date: 22nd June 2017

Enhancements included in this release:

  • The stemcell has been updated to the 3363 line.

1.3.4

Release Date: 24th March 2017

Enhancements included in this release:

  • Security for the Config Server’s encryption capabilities has been increased.
  • Made timeout value for waiting on service instance creation configurable via the tile’s configuration page.

1.3.3

Release Date: 30th January 2017

Enhancements included in this release:

  • The stemcell has been updated to 3263.17. This resolves the following issues:
  • The Config Server now exposes the /encrypt endpoint to generate encrypted property values based on a provided key.
  • The /info endpoint, accessed on the service broker applications or on service instance backing applications, now returns version information for the corresponding build of Spring Cloud Services.

1.3.2

Release Date: 21st December 2016

Enhancements included in this release:

  • Error reporting in the Spring Cloud Services tile’s “Smoke Tests” errand has been improved.
  • The Spring Cloud Services service broker now returns a message for each of any errors encountered by the cf create-service and cf update-service commands.

Fixes included in this release:

  • A timeout issue that could occur during the push operation for service instance backing applications has been resolved.

1.3.1

Release Date: 7th December 2016

Important: If you upgrade to this release of Spring Cloud Services, you must ensure that your client applications which use the Service Registry do not set the eureka.instance.virtualHostName or eureka.instance.secureVirtualHostName properties to different values from that of the eureka.instance.appname property.

Enhancements included in this release:

  • The Spring Cloud Services broker has been upgraded to Spring Cloud Camden.SR3.
  • Spring Cloud Services service instance backing applications now print a custom Spring Boot banner on startup.
  • If a Service Registry client application’s eureka.instance.secureVirtualHostname or eureka.instance.virtualHostname properties are set and do not match the application’s eureka.instance.appname property, the Spring Cloud Services connector for Service Registry now prevents application startup and logs an error message. For more information, see the Eureka Application Name Configuration section of the Spring Cloud Connectors topic in the Service Registry documentation.

Fixes included in this release:

  • The Service Registry now supports servers which use Server Name Indication (SNI) to serve multiple SSL certificates.

1.3.0

Release Date: 10th November 2016

Important: Spring Cloud Services 1.3.0 requires version 3.8 or later of the Cloud Foundry Java buildpack. If your Pivotal Cloud Foundry deployment is using an older version of the Java buildpack, upgrade it before installing this release.

Enhancements included in this release:

  • Spring Cloud Services now supports Pivotal Cloud Foundry versions 1.7 and later.
  • Spring Cloud Services now uses a floating stemcell for enhanced security. For more information, see the Understanding Floating Stemcells topic in the Pivotal Cloud Foundry documentation.
  • The validation normally performed by Spring Cloud Services for the Pivotal Cloud Foundry® Elastic Runtime SSL certificate can now be disabled by operators in the tile’s settings. See step 5 of the Installation Steps in the Installation topic for more information.
  • The Spring Cloud Services broker has been upgraded to Spring Boot 1.4.1 and Spring Cloud Camden.SR2.
  • Service instances are now based on Spring Cloud Camden.SR2, and client applications can use Spring Boot 1.3.x–1.4.1 and Spring Cloud Brixton.x–Camden.SR2. For more information about client application dependencies, see Client Dependencies.

Note: Spring Cloud Services 1.3.0 is compatible with Spring Boot versions 1.3.x–1.4.x, but is based on Spring Cloud Camden, which builds on Spring Boot 1.4. In client applications, Spring Boot 1.4.x is recommended for optimum experience with this release.

Create a pull request or raise an issue on the source for this page in GitHub