Fixes geerlingguy#347: Fix replication deprecation warnings.

Author: geerlingguy

README.md

@@ -118,9 +118,9 @@ The rest of the settings in `defaults/main.yml` control MySQL's memory usage and
     mysql_expire_logs_days: "10"
     mysql_replication_role: ''
     mysql_replication_master: ''
-    mysql_replication_user: []
+    mysql_replication_user: {}
 
-Replication settings. Set `mysql_server_id` and `mysql_replication_role` by server (e.g. the master would be ID `1`, with the `mysql_replication_role` of `master`, and the slave would be ID `2`, with the `mysql_replication_role` of `slave`). The `mysql_replication_user` uses the same keys as `mysql_users`, and is created on master servers, and used to replicate on all the slaves.
+Replication settings. Set `mysql_server_id` and `mysql_replication_role` by server (e.g. the master would be ID `1`, with the `mysql_replication_role` of `master`, and the slave would be ID `2`, with the `mysql_replication_role` of `slave`). The `mysql_replication_user` uses the same keys as individual list items in `mysql_users`, and is created on master servers, and used to replicate on all the slaves.
 
 `mysql_replication_master` needs to resolve to an IP or a hostname which is accessable to the Slaves (this could be a `/etc/hosts` injection or some other means), otherwise the slaves cannot communicate to the master.
 

tasks/replication.yml

@@ -8,7 +8,7 @@
     state: present
   when:
     - mysql_replication_role == 'master'
-    - mysql_replication_user
+    - mysql_replication_user.name is defined
     - mysql_replication_master != ''
   tags: ['skip_ansible_galaxy']
 
@@ -46,8 +46,8 @@
   when:
     - (slave.Is_Slave is defined and not slave.Is_Slave) or (slave.Is_Slave is not defined and slave is failed)
     - mysql_replication_role == 'slave'
+    - mysql_replication_user.name is defined
     - mysql_replication_master != ''
-    - mysql_replication_user
 
 - name: Start replication.
   mysql_replication: mode=startslave