# Ansible.mysql replaces community.mysql

**URL:** <https://forum.ansible.com/t/ansible-mysql-replaces-community-mysql/45798>\
**Category:** Project Discussions\
**Tags:** mysql, community-wg\
**Created:** [May 14, 2026, 1:59pm UTC](https://forum.ansible.com/t/ansible-mysql-replaces-community-mysql/45798 "2026-05-14T13:59:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [May 14, 2026, 1:59pm UTC](https://forum.ansible.com/t/ansible-mysql-replaces-community-mysql/45798/1 "2026-05-14T13:59:36Z")

</div>

As mentioned in [The Bullhorn #227](https://forum.ansible.com/t/45785#p-139388-communitymysql-421-release-10), `community.mysql` is replaced by `ansible.mysql`. This means we will add `ansible.mysql` to the Ansible Commnity Package (already [done](https://github.com/ansible-community/ansible-build-data/pull/675), just not released yet) and, in the long run, remove `community.mysql`. The removal will probably happen in Ansible 16.

I’ve opened this thread to discuss any question about this.

For the record, originally the plan was to [certify community.mysql on automation hub](https://forum.ansible.com/t/45709). But it turned out that renaming / moving `community.mysql` to `ansible.mysql` would be better.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [May 14, 2026, 2:09pm UTC](https://forum.ansible.com/t/ansible-mysql-replaces-community-mysql/45798/2 "2026-05-14T14:09:57Z")

</div>

Maybe someone could answer [the question](https://forum.ansible.com/t/45709/11) from @chris here:

> [@Certification of community.mysql collection on Automation Hub](https://forum.ansible.com/t/certification-of-community-mysql-collection-on-automation-hub/45709/11):
>
> Can both `community.mysql` and `ansible.mysql` be installed on the Ansible controller and if both are does it result in one or the other being used depending on the prefix used by a role?

---

<div class="post-metadata">

**Author:** ![bcoca](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bcoca/32/9269_2.png) [@bcoca](https://forum.ansible.com/u/bcoca)\
**Post date:** [May 14, 2026, 2:16pm UTC](https://forum.ansible.com/t/ansible-mysql-replaces-community-mysql/45798/3 "2026-05-14T14:16:04Z")

</div>

You can install multiple collections, the one used is clear if using fqdn, if using ‘bare’ , it will use the community one as that is what core redirects to since 2.10. You CAN have a redirect from there to the ansible one.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [May 14, 2026, 2:18pm UTC](https://forum.ansible.com/t/ansible-mysql-replaces-community-mysql/45798/4 "2026-05-14T14:18:30Z")

</div>

Now that a method for migration has been decided (and implemented), it’s possible to answer this 😉 Both can be installed; the latest community.mysql 5.0.1 release has no more content, but redirects everything to ansible.mysql. So existing playbooks and roles shoud keep working.

(There are no runtime deprecation warnings about which FQCNs to change, though.)