Static Credentials Broker 2.2.0.RELEASE

I'm pleased to announce the release candidate of the Static Credentials broker, version 2.2.0.RELEASE.
This release includes :

• support for route service configuration
• support for application.yaml deployment through env vars

For a more detailed look at the changes in 2.2.0.RELEASE, please take a look at the commit log.

This release can be a drop in replacement with existing 2.1.0.RELEASE.

Static Credentials Broker 2.1.0.RELEASE

I'm pleased to announce the release candidate of the Static Credentials broker, version 2.1.0.RELEASE.
For a more detailed look at the changes in 2.1.0.RELEASE, please take a look at the commit log.

Static Credentials Broker 2.1.0.RC1

I'm pleased to announce the release candidate of the Static Credentials broker, version 2.1.0.RC1.
For a more detailed look at the changes in 2.1.0.RC1, please take a look at the commit log.

v2.0

The 2.X config syntax is not backward compatible. It only supports Diego backends. To use static-creds with DEA backends, prefer the latest 1.X release and its associated documentation.

Check Readme.md for fully documented details for 2.X configuration syntaxt.

version 1.3

new features

• Support external yaml configuration file application.yml as an alternative to configurate the broker.
• Support externalized remote config in git.

fixes

• Supports DEA backends
• Fix: generate plan default description and name from planid instead of same static string;
• Fix: when plan have only credentials definition not any catalog definition, broker should set plan default catalog definitions.
• Fix: broker should fail fast when a plan have no credential definition in configuration.

misc

• Refactor acceptance test: remove logic of parsing configuration file, use hard-coded test data instead.
• In acceptance test, add test case service_broker_updatable to make sure that service broker still works after we change service configuration and restart the broker.
• Add concourse pipeline for running acceptance test.
• Provide template for deployment and property configuration files: manifest.tmpl.yml, manifest.tmpl.yaml-config.yml manifest.tmpl.remote-config.yml, and application.tmpl.yml

version 1.2

reduce documentation upgrade effort on release (minor)

version 1.1

support for multiple services and plans with associated credentials

version 1.0

initial release