Tanzu Cloud Service Broker for Microsoft Azure 1.3

1.12 1.11 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 1.2 1.1 1.0

Release Notes for Cloud Service Broker for Azure

Last Updated October 24, 2024

This topic describes the changes in this minor release of Tanzu Cloud Service Broker for Azure.

v1.3.1

Release Date: 08 November 2022

Resolved issues

This release has the following fixes:

  • Service offering logos now show up in Apps Manager: Previously when provisioning services through Apps Manager, service logos did not appear. This made it difficult to identify the offering from similar ones installed on the platform. Service offerings now display a generic Tanzu logo.

  • Fixed issue with limits to environment variables length when installing the tile: In previous versions, the broker deployed by the tile was configured through environment variables. This caused environments with lengthy configurations to hit a limit on the size of environment variables. From this version, the tile uses a configuration file written during the deployment process that overcomes such limits. No action is needed.

  • Fixed issue with upgrading Azure SQL Failover DB Group instances that had existing property set to true: When an Azure SQL Failover DB Group instance was created with the property existing set to true the upgrade process failed because it attempted to import values that were never set. The upgrade now succeeds and there are no attempts to import values.

  • MSSQL Run Failover service client secret parameter is no longer exposed on error: csb-azure-mssql-fog-run-failover is no longer exposed. The value of the client secret is considered a sensible field. Its value is not logged in plain text.

  • MSSQL Run Failover service parameters validation is more flexible: csb-azure-mssql-fog-run-failover is more flexible. Previously, the validation of the parameters was carried out in a more restrictive way, demanding rigidity of the admitted values. With this change, the main validation is on the supplier side, and there is only a check if the field is empty.

Known issues

This release has the following issue:

  • Values containing single ticks break broker configuration: If the tile provided value contains ', Tanzu Cloud Service Broker for Azure cannot parse the generated broker configuration. To prevent this issue, replace the wrapping ' with YAML multiline notation.

  • Azure PostgreSQL and Azure MySQL binding credentials contain invalid URIs: The URI and JDBC attributes in the binding credentials include an @ character in the user name for these services. This can cause parsing or client libraries to fail due to validations because @ is a reserved character in the URI specification and must be URI-encoded.

  • Attempting to delete an already deleted binding fails: When attempting to delete a binding that does not exist, Cloud Service Broker for Azure returns an HTTP 500 code instead of the HTTP 410 required by the Open Service Broker API (OSBAPI) specification. This causes issues when the platform times out waiting for the delete operation to be completed on the IaaS, which results in the binding not being deleted from the platform. Further attempts to remove the binding fail because it is deleted from the broker database.

v1.3.0

Release Date: 05 August 2022

Features

New features and changes in this release:

Known Issues

This release has the following issues:

  • Incompatible changes upgrading some services from some versions: Some services cannot be upgraded from previous versions. For more information, see Issues with Upgrading Service Instances to v1.3.

  • Failure to upgrade Azure SQL Failover DB Group instances that have existing property set to true: The upgrade process attempts to import values for resources that don’t exist.

  • Limits to environment variables length when installing the tile: The broker deployed by the tile is configured through environment variables. This causes installations with several plans or other lengthy configurations to hit a limit on the size of environment variables in the platform. This limit prevents the broker app from starting, which causes the deployment to fail.

  • Azure PostgreSQL and Azure MySQL binding credentials contain invalid URIs: The URI and JDBC attributes in the binding credentials include an @ character in the user name for these services. This can cause parsing or client libraries to fail due to validations because @ is a reserved character in the URI specification and must be URI-encoded.

  • Attempting to delete an already deleted binding fails: When attempting to delete a binding that does not exist, Cloud Service Broker for Azure returns an HTTP 500 code instead of the HTTP 410 required by the Open Service Broker API (OSBAPI) specification. This causes issues when the platform times out waiting for the delete operation to be completed on the IaaS, which results in the binding not being deleted from the platform. Further attempts to remove the binding fail because it is deleted from the broker database.

View Release Notes for Another Version

To view the release notes for another product version, select the version from drop-down menu at the top of this page.