You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ansible warns about the sudo: yes flag in install.yml:
[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and make sure become_method is 'sudo'
(default).
This feature will be removed in a future release.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: