Ansible.mysql replaces community.mysql

Project Discussions
,
1

As mentioned in The Bullhorn #227, community.mysql is replaced by ansible.mysql. This means we will add ansible.mysql to the Ansible Commnity Package (already done, 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. But it turned out that renaming / moving community.mysql to ansible.mysql would be better.

2

Maybe someone could answer the question from @chris here:

1 Like
3

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.

1 Like
4

Now that a method for migration has been decided (and implemented), it’s possible to answer this :wink: 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.)

2 Likes