v0.26.1

v0.26.1

Release Date: February 22, 2019

Features

New features and changes in this release:

• Updated the minimum BOSH versions for the recreate-all-service-instances errand to satisfy OpsManager 2.2 environments, which require BOSH 266.15.0+, and OpsManager 2.3 environments, which require BOSH 267.9.0+.
• Bumped the On Demand Services SDK to integrate a change where deleting a binding can use BOSH DNS addresses.

Known Issues

• v0.26.0 introduced Dynamic BOSH Configuration. This is not supported in BOSH for BOSH team users in Ops Manager versions 2.1 and earlier. For these environments, you should disable Dynamic BOSH Configuration by setting the disable_bosh_configs property to true in the broker job.

Minimum Version Requirements

The following are minimum version requirements for this release:

• BOSH v266.12.0 or v267.6.0 and later
• Cloud Foundry v238 and later

For Pivotal Cloud Foundry (PCF) version support, see Product Snapshot.

v0.26.0

Breaking changes

• On-demand services SDK users: In an effort to minimise future breaking changes to the SDK interfaces, we have refactored the existing functions to take data structures rather than positional parameters. That means that the signature of every function has changed, but hopefully they will be more stable now.

Features

New features and changes in this release:

• Service adapters can now return multiple BOSH configs (for example, cloud-config or runtime-config) when generating their manifests. These configs will be applied before deploying and will only be available for that particular deployment. Configs are deleted when a deployment is deleted.
• The register-broker errand spec now uses the broker link to configure CF. The following properties can be removed from the errand job in your manifest as they will be silently ignored: cf.api_url, cf.admin_username, cf.admin_password.
• The service catalog on the broker now returns maintenance_info, which can be used to trigger a single-instance upgrade in the broker. Platforms can now implement functionality needed to expose this feature.
• The recreate-all-service-instances errand now triggers service instance post-deploy errands. Supported versions: OpsManager 2.2.16+ (BOSH Director 266.10.0+), OpsManager 2.3.10+ (BOSH Director 267.10.0+), OpsManager 2.4.3+ (BOSH Director 268.2.2+), OpsManager 2.5+ (BOSH Director 268.4.0+).
• Upgrade golang to v1.11.5.

Known Issues

There are no known issues for this release.

v0.25.0

Features

New features and changes in this release:

• Introduces a new errand recreate-all-service-instances. This should be added to service broker manifests to enable operators to recreate all service instances managed by a broker. If your broker has lifecycle errands configured, these will NOT be run by the recreate-all-service-instances errand. We plan to implement this functionality in a future release. This errand may be useful for:

  • performing a seamless rotation of the Ops Manager root CA. For further information, see the Ops Manager cert rotation docs.
  • performing a full restore of the platform, such as during disaster recovery or migrations.

• Adds a new configuration option for the cf_service_access broker property. This allows brokers to be configured to enable service access for a single org only. Previously it was only possible to enable access either for all or no orgs.

• Upgrades golang to v1.11.2

Breaking Changes

There are no breaking changes in this release.

Known Issues

There are no known issues for this release.

0.24.0

Breaking Changes

• Service Instances API configuration has moved from the upgrade-all errand to the broker job. For more information, see Features below.
• GenerateManifest method in the Service Adapter takes a new parameter previousSecrets containing secrets from the previously deployed service instance manifest.

Features

New features and changes in this release:

• The orphan-deployments errand can use the Service Instances API. This change only impacts brokers that are installed without Cloud Foundry. The configuration for this was previously on the update-all-service-instances errand, and has been moved to the broker job.
• The same configuration is used for both the orphan-deployments and upgrade-all errands.
• CredHub CLI library was bumped to allow use with both v1 and v2 CredHub servers. This change is required to use PCF 2.4 and onwards
• Upgrades golang to v1.11.2
• New previousSecrets parameter to GenerateManifest() in the Service Adapter

v0.23.0

Bump brokerapi on sdk and example adapters [#160477667]

Signed-off-by: Derik Evangelista <[email protected]>
Co-authored-by: Derik Evangelista <[email protected]>