v5.1.0

Added

• New services for running MySQL and PostgreSQL CloudSQL in a VPC.

Changed

• Updated database versions for CloudSQL.
• Default PostgreSQL version is now POSTGRES_11
• Removed BigTable sizing restrictions due to improvements in Google Cloud.
• Use Go 1.14

Possible Fix for #549

This is a testing release for a form change to fix #549. It appears OpsMan has changed behavior when attempting to apply forms from the CLI to where it no longer accepts certain configurations that are valid in the GUI. This change relaxes those constraints to give a worse GUI experience that should (hopefully) fix the issue with the CLI.

v5.0.0

Added

• PostgreSQL 11 Support
• Support setting database flags (new configuration parameter: database_flags).
• Support setting the storage auto resize limit (new configuration parameter: auto_resize_limit).

Fixed

• CloudSQL instances can be configured with high availability again (new configuration parameter: availability_type).

Removed

• Support for MySQL 5.5.
• Support for first generation CloudSQL instances and their associated fields.

v4.4.0

Fixed

• Fixed custom plans from the tile not working.
• Fixed JDBC URI issues

Added

• Built-in support for Redis.
• Built-in support for Filestore.

v4.3.0

Fixed

• Fix bug that caused SQL users to never be deleted.
• "data too long" error for existing service broker installations when passing service provisioning configuration > 255 characters (#468)

Changed

• Built Brokerpaks now have a name of {name}-{version}.brokerpak as defined by the manifest rather than the name of the parent directory.
• Services inside Brokerpaks now have a file name that includes their CLI friendly name to help differentiate them.
• The pak build command now includes progress logs.
• An unbind of a service now fails as early as possible to prevent partial deletions.

Added

• Ability for plans to selectively override user variables.
• Ability to get plan information from HIL execution environment on bind.

4.2.2

[4.2.2] - 2019-02-06

Fixed

• The pak run-examples sub-command now returns a non-zero status code on failure.
• JSONSchema validation no longer fails due to erroneous duplicate required fields.
• Brokerpaks no longer use incorrect templates due to an invalid pointer.

v4.2.0

[4.2.0] - 2019-01-04

Security

• The broker uses a Pivotal library affected by CVE-2018-15759. Until the library is updated, it's recommended that you not run the service broker on a public network. If you must run it on a public network, make it accessible through a proxy that supports fail2ban.

Added

• The ability to enable/disable services based on product lifecycle tags. See #340 for context.
• Preview support for Firestore.
• Preview support for Dialogflow.
• Preview support for Stackdriver Metrics.
• Namespace support for Datastore.
• Preview support for Dataflow.
• Default roles for ML, BigQuery, BigTable, CloudSQL, Pub/Sub, Spanner, and Cloud Storage.
• /docs endpoint that serves docs for your installation.
• Preview support for Dataproc via brokerpaks.
• Varcontext now supports casting computed HIL values.
• New regional and multi-regional Cloud Storage plans.
• Ability to expose JSONSchema in the service catalog by enabling the enable-catalog-schemas flag.

Changed

• Support links for services now point to service-specific pages where possible.
• Feature flags are now handled through a generic toggles framework. Option labels and descriptions might change slightly in the tile.
• Service definitions now get field-level validation to check for sanity before being registered.

Removed

• The examples/ directory.

Fixed

• Fixed machine types for PostgreSQL to use custom but keep the old names for compatibility.

v4.1.0

Added

• Pub/Sub now adds default labels to created topics and subscriptions.
• New validation documentation for Pub/Sub.
• Ability for operators to override the provision defaults with fixed values.
• New form to let operators set provision defaults.
• New coldline Cloud Storage plan.
• Ability to create custom Cloud Storage plans.
• New tile form for creating custom Cloud Storage plans.
• Examples of binding variables to the docs.
• Constraints/validation of the binding variables to the docs.
• New version sub-command to show the current version of the binary.
• New generate sub-commands to generate the tile.yml and manifest.yml files.

Changed

• Role whitelists are now validated through JSON Schema checks.
• The run-examples sub-command now evaluates the credentials against the JSON Schema, improving robustness.

Fixed

• Fixed issue where Cloud Datastore service accounts were getting the same name.

v4.0.0

Note: if you're upgrading from 3.x, follow the upgrading docs to ensure your plans continue to work.

Added

• New sub-command plan-info to dump plan information to the console.
• New sub-command client to execute documentation examples and interact with the broker.
• New sub-command help which outputs help documentation.
• New sub-command config which can convert between configuration file formats.
• New sub-command generate to generate use, tile forms, and configuration documentation.
• New sub-command serve to run the service broker server.
• New sub-command show to dump database state.
• The ability to configure the system with YAML, TOML, properties, or JSON configuration files via the --config flag in conjunction with using environment variables.
• The ability to customize the database name in the Tile.
• The ability to turn on/off services via environment variable.
• Default plans for Spanner, BigTable, and CloudSQL.
• Whitelists for bindings so only certain "safe" roles can be chosen by end-users.
• Automatic labeling of resources with organization GUID, space GUID, and instance ID to BigQuery, CloudSQL, Spanner, and Cloud Storage.

Deprecated

• Running the service by executing the main executable. Use the serve sub-command instead.

Changed

• Breaking plan ids are now required and will not be generated if not supplied.
• Breaking changed custom plan id field name from guid to id.
• Breaking modified "features" plan configuration field name to "service_properties".
• Breaking modified structure of all catalog-related environment variables - plans is now a sub-field of the Service object,
  and Service objects are defined individually by setting environment variables like GOOGLE_<SERVICE_NAME>
• You no longer have to specify service information in the manifest.
• Breaking The Cloud Storage plan reduced_availability was changed to reduced-availability to be compliant with the spec and work with Kubernetes.
• Tables are created only if they do not exist on migration, fixing #194.
• The broker now adheres to Open Service Broker API version 2.13.
• Improved ORM migrations and test coverage with SQLite3.

v 3.3.0 Tile

Added Stackdriver Debugger and Trace support