Edit

MySQL resource provider 2.0.6.x release notes

These release notes describe the improvements and known issues in MySQL resource provider version 2.0.6.x.

Build reference

Starting with this release, MySQL resource provider is a standard Azure Stack Hub value-add RP. To access the MySQL resource provider in Azure Stack Hub marketplace, open a support case to add your subscription to the allowlist.

The resource provider has a minimum corresponding Azure Stack Hub build. The minimum Azure Stack Hub release version required to install this version of the MySQL resource provider is listed in the following table.

Apply the minimum supported Azure Stack Hub update to your Azure Stack Hub integrated system before deploying the latest version of the MySQL resource provider.

Supported Azure Stack Hub version MySQL resource provider version
Version 2108, 2206 MySQL RP version 2.0.6.x

Important

If an existing version of MySQL resource provider is running in your system, make sure to update it to version 1.1.93.x, before upgrading to this latest version.

New features and fixes

This version of the Azure Stack Hub MySQL resource provider includes the following improvements and fixes:

  • Installation and future version upgrade come from the Azure Stack Hub marketplace.
  • A specific version of Add-on RP Windows Server is required. The correct version of Microsoft AzureStack Add-On RP Windows Server is automatically downloaded if you install the resource provider in connected environment. In disconnected environment, make sure you download the right version of Microsoft AzureStack Add-On RP Windows Server image before deploying or upgrading to this version of the MySQL resource provider.
  • Receive alerts when certifications are about to expire. For more informaiton, see Secrets rotation.
  • Other bug fixes.

Known issues

After deployment or upgrade, Azure Stack Hub operators need to manually register their default provider subscription to the tenant namespace (Microsoft.MySQLAdapter) before they can create login or databases.

Next steps