Azure MySQL Flexible Servers Management Client Library for Python

Warnings

• breaking Migration from `azure-mgmt-rdbms`: The `azure-mgmt-rdbms` library's MySQL single server management is deprecated. Users should migrate to `azure-mgmt-mysqlflexibleservers` for managing MySQL Flexible Servers as soon as possible.
  Fix: Update your import statements and client initialization to use `azure-mgmt-mysqlflexibleservers` instead of `azure-mgmt-rdbms`.
• breaking Authentication system revamp: Older credential mechanisms like `azure.common.credentials` or `msrestazure.azure_active_directory` are no longer supported across Azure SDKs.
  Fix: Migrate to `azure-identity` classes, specifically `DefaultAzureCredential`, for authentication. Ensure relevant environment variables (e.g., `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_SECRET`, `AZURE_SUBSCRIPTION_ID`) are configured.
• breaking Model `OperationProgressResult` instance variable `object_type` moved under `properties`; `Provisioning` model deleted. This introduces API changes in `1.0.0` compared to earlier beta versions.
  Fix: Review code that interacts with `OperationProgressResult` and adjust access to `object_type` if directly accessed. Remove any references to the `Provisioning` model.
• gotcha TLS 1.0/1.1 connections denied: Azure Database for MySQL Flexible Server enforces TLS 1.2 by default. Older clients attempting to connect with TLS 1.0 or 1.1 will be denied.
  Fix: Update your client applications and drivers to support TLS 1.2 or higher. Verify your connection strings and client configurations.
• gotcha Lack of `SUPER` privilege and `DBA` role: The Azure Database for MySQL Flexible Server service does not support `SUPER` privilege or `DBA` role. Operations requiring these privileges will fail.
  Fix: Adjust application logic to avoid operations that require `SUPER` privilege. Review and update stored procedures, triggers, or schema imports that might implicitly rely on these privileges.

Install

• pip install azure-mgmt-mysqlflexibleservers azure-identity Install with pip

Imports

• MySQLManagementClient

  from azure.mgmt.mysqlflexibleservers import MySQLManagementClient

• DefaultAzureCredential

  from azure.identity import DefaultAzureCredential

Quickstart

This quickstart demonstrates how to authenticate with Azure using `DefaultAzureCredential` and then initialize `MySQLManagementClient` to interact with your Azure MySQL Flexible Servers. Ensure `AZURE_SUBSCRIPTION_ID` and other Azure Identity environment variables (like `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_SECRET` for service principal authentication) are set for `DefaultAzureCredential` to function properly.

import os
from azure.identity import DefaultAzureCredential
from azure.mgmt.mysqlflexibleservers import MySQLManagementClient

# Set environment variables for authentication:
# AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET (for service principal)
# AZURE_SUBSCRIPTION_ID

subscription_id = os.environ.get('AZURE_SUBSCRIPTION_ID', 'YOUR_SUBSCRIPTION_ID')

# Authenticate using DefaultAzureCredential
# This credential type tries multiple authentication methods, like environment variables or managed identity.
credential = DefaultAzureCredential()

# Create a MySQLManagementClient instance
client = MySQLManagementClient(credential=credential, subscription_id=subscription_id)

# Example: List all MySQL Flexible Servers in the subscription
print(f"Listing MySQL Flexible Servers in subscription: {subscription_id}")
for server in client.servers.list():
    print(f"- Server Name: {server.name}, Resource Group: {server.resource_group}")

# For more operations, use client.servers, client.databases, etc.
# e.g., print(client.servers.get(resource_group_name='myResourceGroup', server_name='myServerName'))