These are release notes for Cloud Service Broker for Azure.

v1.1.9

Release Date: June 9, 2021

Breaking Change: If you use the small plans of csb-azure-mssql or csb-azure-mssql-failover-group, then, after installing v1.1.9, update your service instances to use new versions of those plans. See Updating from v1.1.8 and Earlier.

Features

New feature in this release:

• Support for Private Endpoints in MySQL and Redis offerings: Creating Private Endpoints during the provisioning of MySQL and Redis instances is now supported. See pull request #33 in GitHub.

Resolved Issues

This release has the following fixes:

• Cloud Service Broker for Azure v1.1.9 is compatible with VMware Tanzu Application Service for VMs v2.11: You cannot install earlier versions of Cloud Service Broker for Azure on VMware Tanzu Application Service for VMs v2.11.

• Subsuming failover groups: Fixed an issue that caused unexpected database deletion in some failure cases. For information, see Issue #10 in GitHub.

• Updating Azure SQL Failover Group instances: Fixed an issue where the service plan could not be updated. For information, see Issue #20 in GitHub.

• MySQL database instance firewall/authorized network rules: Fixed an issue where MySQL instance creation failed intermittently when authorized_network was configured.

• Broker logs contain the correlation ID: Log entries relating to a request now show a correlation ID so that lines can be differentiated when there are concurrent requests.

Known Issues

This release has the following issue:

• Parameters specified during service instance updates are not persisted by subsequent updates: If you update a service instance and change a parameter, then the next time that you update the service instance, you must specify the same parameter again. Otherwise, the parameters revert to the values that they had when the service instance was created. For more information, see Bug #178213626 in Pivotal Tracker.

v1.1.8

Release Date: January 28, 2021

Resolved Issues

This release has the following fix:

• App binding credentials now work after performing a failover of Azure SQL DB: When creating a csb-azure-mssql-db-failover-group instance and binding to an app, the login was created in the primary database, and so did not get replicated to the secondary database. For more information, see Issue #4 in GitHub.

Known Issues

This release has the following issues:

• Installation on VMware Tanzu Application Service for VMs v2.11 fails: Installation fails because the csb-azure-mssql-failover-group/small plan and the csb-azure-mssql/small plan have the same ID. For more information, see Pull Request #34 in GitHub.

• Parameters specified during service instance updates are not persisted by subsequent updates: If you update a service instance and change a parameter, then the next time that you update the service instance, you must specify the same parameter again. Otherwise, the parameters revert to the values that they had when the service instance was created. For more information, see Bug #178213626 in Pivotal Tracker.

v1.1.7

Release Date: January 4, 2021

Resolved Issues

This release has the following fix:

• Changing the SQL admin password no longer breaks bind and unbind operations: Changing the SQL admin password no longer causes bind and unbind operations to fail for existing instances.
  
  However, you might need to subsume instances that are still failing to bind and unbind. For how to subsume an instance, see Subsuming a Microsoft Azure Service Broker MSSQL Database Instance or Subsuming a Microsoft Azure Service Broker MSSQL Failover Group Instance.
  
  For additional information about the issue, see Issue #158 in GitHub.

Known Issues

This release has the following issue:

• Installation on VMware Tanzu Application Service for VMs v2.11 fails: Installation fails because the csb-azure-mssql-failover-group/small plan and the csb-azure-mssql/small plan have the same ID. For more information, see Pull Request #34 in GitHub.

• Parameters specified during service instance updates are not persisted by subsequent updates: If you update a service instance and change a parameter, then the next time that you update the service instance, you must specify the same parameter again. Otherwise, the parameters revert to the values that they had when the service instance was created. For more information, see Bug #178213626 in Pivotal Tracker.

v1.1.6

Release Date: December 16, 2020

Features

New features and changes in this release:

• Azure Virtual Network (VNet) integration: VNet is integrated for Azure Redis Cache premium plans.

Resolved Issues

This release has the following fixes:

• Admin username and password for a AzureSQL Failover Group database no longer exposed: create service-key and bind-service on the non-primary site of a AzureSQL Failover Group database no longer exposes the admin username and password.

• Credentials are no longer output in plain text in application console logs.

• Execute permissions no longer denied: Execute permissions previously denied on stored procedures after Azure SQL subsume are now permissible.

Known Issues

This release has the following issues:

• Changing the SQL admin password breaks bind and unbind operations: After changing the SQL admin password and re-deploying the broker, bind and unbind operations for existing database instances fail. For more information, see Issue #158 in GitHub.

• Installation on VMware Tanzu Application Service for VMs v2.11 fails: Installation fails because the csb-azure-mssql-failover-group/small plan and the csb-azure-mssql/small plan have the same ID. For more information, see Pull Request #34 in GitHub.

• Parameters specified during service instance updates are not persisted by subsequent updates: If you update a service instance and change a parameter, then the next time that you update the service instance, you must specify the same parameter again. Otherwise, the parameters revert to the values that they had when the service instance was created. For more information, see Bug #178213626 in Pivotal Tracker.

v1.1.1

Release Date: November 20, 2020

Breaking Change: Subsume is no longer provided as a separate service in Cloud Foundry Marketplace. It is now a plan that is currently only available for the MSSQL Database service.

Features

New features and changes in this release:

• Support for Azure MySQL Threat Detection Policy: For more information about Advanced Threat Protection for Azure Database for MySQL, see the Microsoft documentation.
• Added subsume functionality for Azure MySQL failover group (FoG) instances: For information about subsuming Azure MySQL FoG instances, see Subsuming a Microsoft Azure Service Broker MSSQL Database Fail Over Group Instance in GitHub.

Resolved Issues

This release has the following fixes:

• Data loss when updating services: Any parameters provided to cf create-service are now preserved and used as defaults during cf update-service.

Known Issue

This release has the following issues:

• Changing the SQL admin password breaks bind and unbind operations: After changing the SQL admin password and re-deploying the broker, bind and unbind operations for existing database instances fail. For more information, see Issue #158 in GitHub.

• Installation on VMware Tanzu Application Service for VMs v2.11 fails: Installation fails because the csb-azure-mssql-failover-group/small plan and the csb-azure-mssql/small plan have the same ID. For more information, see Pull Request #34 in GitHub.

• Parameters specified during service instance updates are not persisted by subsequent updates: If you update a service instance and change a parameter, then the next time that you update the service instance, you must specify the same parameter again. Otherwise, the parameters revert to the values that they had when the service instance was created. For more information, see Bug #178213626 in Pivotal Tracker.

v1.1.0

Release Date: November 5, 2020

Breaking Change: Subsume is no longer provided as a separate service in Cloud Foundry Marketplace. It is now a plan that is currently only available for the MSSQL Database service.

Features

New features and changes in this release:

• Provides a cleaner pattern for subsuming existing MSSQL database instances from the Microsoft Azure Service Broker: For more information, see Subsuming a Microsoft Azure Service Broker MSSQL Database Instance.
• Adds support for Azure SQL Short Term Retention Period: For more information about the original issue, see Issue #100 - Control backup retention period for Azure SQL DB in GitHub.
• Error messaging: Adds clearer error messaging to the subsume functionality.

Resolved Issues

This release has the following fixes:

• Azure Storage can now be configured in the tile: Previously, there was an issue where Azure Storage configuration was not shown in the tile.
• Labeling: Fixed incorrect labeling in Azure Redis config.

Known Issues

This release has the following issues:

• Data loss when updating services: Any parameters provided in the cf create-service command must also be provided in the cf update-service command. Otherwise, the broker substitutes default values for those parameters.
  For example, if you provided the parameter db_name when the service was created, omitting this parameter from the update service command resulted in data loss.

• Changing the SQL admin password breaks bind and unbind operations: After changing the SQL admin password and re-deploying the broker, bind and unbind operations for existing database instances fail. For more information, see Issue #158 in GitHub.

• Installation on VMware Tanzu Application Service for VMs v2.11 fails: Installation fails because the csb-azure-mssql-failover-group/small plan and the csb-azure-mssql/small plan have the same ID. For more information, see Pull Request #34 in GitHub.

• Parameters specified during service instance updates are not persisted by subsequent updates: If you update a service instance and change a parameter, then the next time that you update the service instance, you must specify the same parameter again. Otherwise, the parameters revert to the values that they had when the service instance was created. For more information, see Bug #178213626 in Pivotal Tracker.

View Release Notes for Another Version

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