rabbitmq_cluster: Switch how permissions are done and give admin all perms

The way we were granting perms to admin was just on existing vhost/queues.
Instead we should just give admin full privs to any queues/vhosts that might
exist now or later.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2019-09-23 17:26:19 +00:00 committed by Pierre-Yves Chibon
parent 622170c679
commit a9c97618a1

View file

@ -228,19 +228,11 @@
rabbitmq_user:
user: admin
password: "{{ rabbitmq_admin_password_staging }}"
permissions:
- vhost: /
configure_priv: .*
read_priv: .*
write_priv: .*
- vhost: /pubsub
configure_priv: .*
read_priv: .*
write_priv: .*
- vhost: /public_pubsub
vhost: /
configure_priv: .*
read_priv: .*
write_priv: .*
state: present
tags: management
when: env == "staging" and inventory_hostname.startswith('rabbitmq01')
tags:
@ -251,19 +243,11 @@
rabbitmq_user:
user: admin
password: "{{ rabbitmq_admin_password_production }}"
permissions:
- vhost: /
configure_priv: .*
read_priv: .*
write_priv: .*
- vhost: /pubsub
configure_priv: .*
read_priv: .*
write_priv: .*
- vhost: /public_pubsub
vhost: /
configure_priv: .*
read_priv: .*
write_priv: .*
state: present
tags: management
when: env == "production" and inventory_hostname.startswith('rabbitmq01')
tags: