We are pleased to announce the first milestone release of Spring Cloud Open Service Broker 2.0.0.

This project was formerly named Spring Cloud - Cloud Foundry Service Broker. A lot has changed in the few years since that project was released. The service broker API that the project implements is no longer specific to Cloud Foundry but has been donated to the Open Service Broker API project and is implemented by Kubernetes and other platforms. The new project name reflects this evolution and openness.

In addition to a new name, some highlights of the 2.0 version are:

• 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
…

I am pleased to announce the newest addition to the Spring Cloud family. Spring Cloud Cloud Foundry Service Broker is a framework for building service brokers for the Cloud Foundry platform.

Cloud Foundry service brokers

Service brokers provide a means to extend Cloud Foundry with managed services that can be consumed by applications deployed to the platform. Managed services typically expose some sort of resource to an application, such as a database or other persistent store, a messaging system, or other supporting infrastructure. Service brokers publish a catalog of services and service…

I’m pleased to announce the availability of Spring Cloud Connectors 1.2.1. This is a maintenance release with a few new features and a few bug fixes.

Here are the highlights:

Heroku Connector

Relational Databases

• The Heroku cloud connector now recognizes the DATABASE_URL environment variable when detecting PostgreSQL database.

Redis

• Heroku Redis is now supported.

Spring Connector

Relational Databases

• When creating a DataSource, Spring Cloud Connectors will look for a pooling DataSource implementation on the classpath and choose one based on a default priority. The priority of detection has been changed to more closely match the order used in Spring Boot.
• Applications can customize the priority order of pooled DataSource implementations using either Java configuration or XML configuration.
• DataSourceConfig will now accept a map of key/value pairs to allow setting arbitrary properties of the created DataSource. This allows overriding of the default JDBC driver class name and validation query set up by Connectors, in addition to other properties of the DataSource…

I’m pleased to announce the availability of Spring Cloud Connectors 1.2.0.

Applications that use Spring Cloud Connectors, and libraries that extend the core Connectors libraries, should be re-compiled against version 1.2.0. There were no backward-incompatible API changes between version 1.1.1 and 1.2.0, but some internal implementation changes prevent 1.2.0 from being a drop-in replacement for 1.1.1 without re-compiling.

Here's an overview of what's new in 1.2.0:

Additional Databases Supported

The Cloud Foundry Connector and Spring Connector now support IBM DB2 and Microsoft SQL Server…

I’m pleased to announce the availability of Spring Cloud Connectors 1.2.0 RC1.

This release should be fully backward compatible with 1.1.0.RELEASE for applications using the library. Libraries that extend the core Connectors library should be recompiled against 1.2.0 RC1, and may encounter a few small extension API changes. Barring any issues, this will be the only RC before 1.2.0.RELEASE.

Here's an overview of what's new in 1.2.0:

Spring Cloud Connectors Core

AMQP

• AmqpServiceInfo no longer validates that the path element of a URI contains a value, which allows the default RabbitMQ vhost to be used.
• URL validation in AmqpServiceInfo was relaxed such that QPID URL format is supported as well as RabbitMQ URL format.
• AmqpServiceInfo now supports holding a list of URIs for providers that support multiple host connections.
…