The old method of setting the default behavior for become/sudo has
changed in 2.x; fortunately the new way is a bit more elegant
Signed-off-by: Zack Cerza <zack@redhat.com>
15 files changed:
ansible_user: ubuntu
roles:
- ansible-managed
+ become: true
roles:
- common
- nameserver
+ become: true
roles:
- common
- paddles
+ become: true
- hosts: pcp
roles:
- pcp
+ become: true
+++ /dev/null
----
-dependencies:
- - role: sudo
---
dependencies:
- - role: sudo
- role: secrets
- role: users
---
dependencies:
- role: secrets
- - role: sudo
---
dependencies:
- role: secrets
- - role: sudo
- role: users
+++ /dev/null
----
-dependencies:
- - role: sudo
+++ /dev/null
-Sudo
-====
-
-This role is mainly used as a dependancy for others. If you add this role as a dependancy
-to another it will ensure that all tasks in that role will use sudo.
+++ /dev/null
----
-# ensures that sudo will be used for all tasks
-ansible_become: true
---
dependencies:
- role: secrets
- - role: sudo
---
dependencies:
- - role: sudo
- role: users
roles:
- common
- testnode
+ become: true
roles:
- common
- teuthology
+ become: true