Release Notes for Cloud Service Broker for Azure

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

v1.4.2

Release Date: March 21, 2023

This release has the following fixes:

You can now upgrade Azure Redis instances created with Cloud Service Broker for Azure v1.3.1 and earlier: Before v1.4.0, Redis service instances were created with the default Redis version for Azure, but new service instances are created as Redis v6.

This caused an issue when upgrading to v1.4.0 and v1.4.1 because these versions have a redis_version property that was set to Redis v4 by default. It caused an attempt to change a Redis instance from v6 to v4, which failed. In v1.4.2, the default Redis version is no longer set, so the upgrade can succeed.

There are no known issues in this release.

Release Date: January 12, 2023

This release has the following fixes:

Azure PostgreSQL and Azure MySQL binding credentials: The URI and JDBC attributes in the binding credentials now have a URI-encoded user name. This fixes potential issues when validating these attributes because Azure includes an @ character in the user name.
Attempting to delete an already deleted binding is now successful: When attempting to delete a binding that does not exist, Cloud Service Broker for Azure now returns a 410 GONE code as required by the Open Service Broker API (OSBAPI) specification.

This fixes the issue where the platform might timeout waiting for the delete operation to be completed on the IaaS, resulting in the binding not being deleted from the platform, and further attempts to remove it fail because it is deleted from the broker database.

This release has the following issue:

Redis v6 service instances created with v1.3.1 or earlier fail to upgrade: A fix is planned for Tanzu Cloud Service Broker for Azure v1.4.2.

Release Date: December 8, 2022

New features and changes in this release:

Redis version: You can now define the Redis version using the redis_version property as part of a plan definition or during create or update operations. To update Redis instances to v6, see Upgrading Tanzu Cloud Service Broker for Azure.
Brokerpak-provided plans are deprecated: All brokerpak-provided plans for Redis are now deprecated. VMware recommends that you create your custom plans in the tile. All deprecated plans set the Redis version to v4 to keep backwards compatibility.

These plans will be removed from the brokerpak in future releases in favor of custom-defined plans in the tile. To update Redis instances to other plans, see Upgrading Tanzu Cloud Service Broker for Azure.

Cosmos DB SQL can now create private endpoints: You can now define private endpoints for Cosmos DB SQL using the private_endpoint_subnet_id and private_dns_zone_ids properties as part of a plan definition or during create or update operations.

This release has the following fixes:

Apps Manager service images: The logo for each service is now displayed in Apps Manager and other GUI applications.

This release has the following issues:

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 theHTTP 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.
Redis v6 service instances created with v1.3.1 or earlier fail to upgrade: A fix is planned for Tanzu Cloud Service Broker for Azure v1.4.2.

To view the release notes for another product version, select the version from dropdown at the top of this page.