community.mysql 5.0.2 Released - Deprecation Warnings on Module Redirects

Introduction

community.mysql is the Ansible Collection that provides modules and plugins for managing MySQL and MariaDB databases: creating and dropping databases and users, managing grants, replication, configuration variables, and running arbitrary SQL through modules such as mysql_db, mysql_user, mysql_query, mysql_replication, and mysql_variables. Version 5.0.2 has just been published to Ansible Galaxy.

This is the first time this collection is tracked on this blog, so there is no prior known version to diff against here. However, according to the collection's own changelog, 5.0.2 is a small, self-contained patch release.

Whats New

According to the release summary shipped in the changelog, this version is exactly what it says on the tin:

This is a patch release of community.mysql collections which only adds deprecation warnings to module redirects.

In practice, community.mysql ships a number of modules as redirects to their canonical implementation (for example short names that alias to community.mysql.mysql_* modules, or older module names kept around for backward compatibility). This release adds explicit deprecation warnings to those redirected entry points, so playbooks that still reference the old/aliased module names will now surface a warning in the Ansible output pointing users toward the module they should be using instead.

No new modules, no new options, and no behavioral changes to the actual database operations are included in 5.0.2. The only user-visible change is the appearance of deprecation warnings for anyone still invoking modules through the redirected names.

Why It Matters

• Playbooks and roles that reference deprecated/redirected module names will start emitting warnings during ansible-playbook runs.
• This does not break existing automation, it only surfaces a warning to help maintainers plan a migration ahead of the eventual removal of the redirects.
• No action is strictly required to stay compatible, but it is a good moment to check ansible-playbook -vvv output (or CI logs) for new deprecation messages related to community.mysql.

Installing and Verifying

Install the collection from Ansible Galaxy and confirm the version currently installed:

# Install (or upgrade to) community.mysql 5.0.2
ansible-galaxy collection install community.mysql:==5.0.2

# Verify the installed version
ansible-galaxy collection list community.mysql

# Show detailed collection info, including changelog location
ansible-galaxy collection list -vvv | grep -A2 community.mysql

To pin the version explicitly in a requirements.yml file:

cat <<'EOF' > requirements.yml
collections:
  - name: community.mysql
    version: "5.0.2"
EOF

ansible-galaxy collection install -r requirements.yml

After upgrading, run an existing playbook that uses community.mysql modules with increased verbosity to check for any new deprecation warnings related to redirected module names:

ansible-playbook -i inventory site.yml -vvv | grep -i deprecat

Summary

For teams currently relying on any of the redirected/legacy module names within community.mysql, treat these new warnings as an early signal to update playbooks to reference the canonical module names before the redirects are eventually removed in a future major release.