v0.33.0

Features

New features and changes in this release:

• Added support for maintenanceInfo.descripton. See Maintenance Info in the OSBAPI spec.
• Fixed an issue where contacting BOSH Director Links API too many times in parallel would cause some requests to fail during operations such as bind and unbind.
• Bumps Golang to v1.12.9
• Bumps github.com/cloudfoundry/bosh-cli from 3.0.1 to 6.0.0.
  Release notes
• Bumps github.com/xeipuuv/gojsonschema from 8bcffc8 to be09369
• Bumps github.com/cloudfoundry/bosh-utils from 701ecef to 3a87930. Release notes
• Bumps github.com/onsi/ginkgo from 1.10.0 to 1.10.1. Release notes
• Bumps github.com/onsi/gomega from 1.6.0 to 1.7.0. Release notes
• Bumps github.com/coreos/go-semver from 0.2.0 to 0.3.0. Release notes
• Bumps code.cloudfoundry.org/credhub-cli from 434d1d2 to 5eb075f. Release notes
• Bumps github.com/cloudfoundry/bosh-utils from 15c5563 to * 701ecef. Release notes
• Bumps github.com/cloudfoundry/socks5-proxy from 3c6b4eec9c2d16c1dac4c42bdb5f755ba09daff8 to 0.2.0. This release includes the previously tagged commit. Release notes
• Bumps github.com/pivotal-cf/on-demand-services-sdk* from 22e2d44 to 6e48a9c. Release notes
• Bumps github.com/craigfurman/herottp from e0bedde to c546d62. Release notes
• Bumps github.com/pivotal-cf/brokerapi from 6.1.0 to 6.1.1. Release notes
• Bumps github.com/pborman/uuid from 1.1 to 1.2. Release notes
• Bumps code.cloudfoundry.org/lager from 0bfa98e to 54c4f25. Release notes
• Bumps github.com/cheggaaa/pb from 1.0.18 to 3.0.1. Release notes
• Bumps github.com/urfave/negroni from 0.3.0 to 1.0.0. Release notes
• Bumps gopkg.in/yaml.v2 from 287cf08 to 7b8349a.
• Bumps github.com/gorilla/mux from 1.6.2 to 1.7.3. Release notes
• Bumps github.com/cloudfoundry/sonde-go from bb12391 to * b337332. Release notes
• Bumps github.com/onsi/gomega from 1.3.0 to 1.6.0. Release notes

Known Issues

There are no known issues for this release.

On-Demand Broker Release uses the following dependencies versions:

Dependency	Version
Golang	1.12.9

v0.32.0

Features

New features and changes in this release:

• Modified upgrade-all-service-instance errand to go through Cloud Foundry when that is the platform and maintenance info is configured. For more information see upgrade-all-instances documentation.
• SDK users can set UpdateMode in the BOSH Variables block. For more information see Variables Block in the BOSH documentation. Note that this is the preferred method to re-generate credentials and should be used instead of ConvergeVariables. For more information see Features Block in the BOSH documentation.

Known Issues

There are no known issues for this release.

v0.31.1

Bug Fixes

• If you include null plans in your service catalog definition, the broker will no longer fail to deploy.

Features

There are no new features on this release

Known Issues

There are no known issues for this release.

v0.31.0

Features

New features in this release:

Indicator Protocol

• The broker will now publish the number of service instances created per service and per plan to the PCF Healthwatch service. For that, we added indicators to the on demand broker release. For more information about Healthwatch, see Pivotal Cloud Foundry Healthwatch.

Resource quotas

• Resource quotas have a new format. See Setting Resource Quotas for instructions. The previous format is still supported and will be removed in a future release.
• Global and Plan resource quotas metrics are now emitted by the broker. For details on these metrics, see Monitoring Your On-Demand Broker

Known Issues

• If you include null plans in your service catalog definition, the broker will fail to deploy. This issue will be fixed in the next release.

v0.30.0

Features

New feature in this release:

• Previously, the broker binary adopted Bosh Process Manager (BPM) for better job isolation and security. This release introduces BPM for all of the broker errands.

Breaking Change: If broker management errands are not colocated with the broker, each errand job must now include the BPM release.

Breaking Change: If the broker management errands are colocated and you are upgrading from ODB version v0.27.0 or later, no changes are required. However, if your errands are colocated and you are upgrading from an ODB version earlier than v0.27.0, BPM will now need to be included as a release.

Known Issues

There are no known issues for this release.

v0.29.1

Resolved Issues

This release fixes the following issues:

• A regression in the register-broker errand that prevented registration because of missing plans. This regression impacted deployments that use Pivotal Application Service (PAS). Enterprise Pivotal Container Service (Enterprise PKS) deployments were not affected by this issue.
• A deregister-broker errand issue that caused the errand to fail when the broker did not exist. This fix causes the errand to behave like other broker errands do in this situation.
• An issue in the delete-all-service-instances and delete-all-service-instances-and-deregister-broker errands that caused them to fail when encountering a service instance that is already being deleted. The errands now skip such instances and continue to issue delete commands for the remaining instances.
• A broker regression that caused the Broker API version information in request headers to not be validated.
• An issue that prevented platform users seeing errors caused by JSON Schema Validation during create, update, and bind errands.

Known Issues

There are no known issues for this release.

v0.29.0

Features

New features and changes in this release:

• The register-broker errand has been converted from a bash script into a golang binary.
  This allows the team to test functionality better and remove unnecessary dependencies.
• Previously, the broker introduced maintenance_info on the service catalog, which can be used to
  trigger a single-instance upgrade in the broker. Now, maintenance_info includes a new version property.
  Platforms can implement functionality needed to expose this feature.
• In the event that a BOSH service deployment becomes unresponsive and the broker's
  standard delete request fails, passing ?force=true as a query parameter to the
  deprovision endpoint will issue a force delete for the BOSH deployment.
  In this case, the broker does its best to run any pre-delete errands configured
  for the deployment. However, if the errand fails, the broker will ignore the
  failure and continue with the next operation (the next pre-delete errand or the force deletion).
• Golang is upgraded to v1.12.5.

Breaking Changes

• When registering plans as org-restricted, previously there was a global organization
  definition in the register-broker errand configuration. This should now be
  configured for each plan in the broker service_catalog with the property service_access_org.
• Previously, enable_service_access was configured in the register-broker errand
  to set service access for all plans. This functionality has been removed. Now, access is defined
  only at the plan level and defaults to enabled.

Known Issues

There are no known issues for this release.

v0.28.0

Features

New features and changes in this release:

• Golang is upgraded to v1.12.4
• SDK Users: added Placement Rules for include and exclude directives as part of addons in BOSH manifest.
• Broker and errand can now be deployed over HTTPS

v0.27.0

Breaking Change

• To support multiple stemcells for a service deployment, the On Demand Services SDK has replaced ServiceDeployment.Stemcell with ServiceDeployment.Stemcells. See the change here.
• The broker now uses BPM. Ensure to configure the broker job with service_adapter.mount_path with a list of filesystem paths to the files (for example, config files) used by the service adapter. Future work will be done to include BPM on errands.

Features

New features and changes in this release:

• ODB now supports service instance deployments that use different stemcells for different instance groups.
• Broker job now uses BPM

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.