MySQL resource provider 184.108.40.206 release notes
These release notes describe the improvements and known issues in MySQL resource provider version 220.127.116.11.
Download the MySQL resource provider binary and then run the self-extractor to extract the contents to a temporary directory. 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 below:
Minimum Azure Stack Hub version MySQL resource provider version Version 1808 (1.1808.0.97) MySQL RP version 18.104.22.168
Apply the minimum supported Azure Stack Hub update to your Azure Stack Hub integrated system or deploy the latest Azure Stack Development Kit (ASDK) before deploying the latest version of the MySQL resource provider.
New features and fixes
This version of the Azure Stack Hub MySQL resource provider includes the following improvements and fixes:
MySQL resource provider portal extension might choose the wrong subscription. The MySQL resource provider uses Azure Resource Manager calls to determine the first service admin subscription to use, which might not be the Default Provider Subscription. If that happens, the MySQL resource provider doesn't work normally.
MySQL hosting server doesn't list hosted databases. User-created databases might not be listed when viewing tenant resources for MySQL hosting servers.
Previous MySQL resource provider (22.214.171.124) deployment could fail if TLS 1.2 isn't enabled. Updated the MySQL resource provider 126.96.36.199 to enable TLS 1.2 when deploying the resource provider, updating the resource provider, or rotating secrets.
MySQL resource provider secret rotation fails. Fixed an issue resulting in the following error code when rotating secrets:
New-AzureRmResourceGroupDeployment - Error: Code=InvalidDeploymentParameterValue; Message=The value of deployment parameter 'StorageAccountBlobUri' is null.
MySQL SKUs can take up to an hour to be visible in the portal. It can take up to an hour for newly created SKUs to be visible for use when creating new MySQL databases.
Reused MySQL logins. Attempting to create a new MySQL login with the same username as an existing login under the same subscription will result in reusing the same login and the existing password.
Workaround: Use different usernames when creating new logins under the same subscription or create logins with the same username under different subscriptions.
Shared MySQL logins cause data inconsistency. If a MySQL login is shared for multiple MySQL databases under the same subscription, changing the login password will cause data inconsistency.
Workaround: Always use different logins for different databases under the same subscription.
Known issues for Cloud Admins operating Azure Stack Hub
Refer to the documentation in the Azure Stack Hub Release Notes.