Closed onitake closed 7 years ago
This is actually a deprecation warning. When Ansible 1.9 added new privilege escalation backends, they changed sudo
to become
. We simply need to rename the parameter.
@onitake Sorry for misunderstanding your original point. Yes, the user should set become
at the playbook level. The role shoudn't elevate permissions itself.
Sorry that I wasn't more clear, but thanks anyway! :)
Ansible warns about the sudo: yes flag in install.yml:
I think it is safe to assume the haproxy role is run with superuser rights, so it doesn't make much sense to have the flag there.