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
This roles uses become to let ansible operate as a privileged user. This is the right and preferred way. But instead of asking for become password, the README recommends to run ansible with sudo:
sudo ansible-playbook -i "localhost," -c local playbook.yml
This doesn't seem to be the right or required practice. For me it resulted in files in my ~/ owned by root a couple of times. Instead, we can tell ansible to ask for password with --ask-become-pass or -K:
ansible-playbook -i "localhost," -c local -K playbook.yml
Also, it seems that ansible-galaxy does not need sudo either:
sudo ansible-galaxy install viasite-ansible.zsh
If you agree, I will throw a pull-request myself.
The text was updated successfully, but these errors were encountered:
This roles uses
become
to let ansible operate as a privileged user. This is the right and preferred way. But instead of asking forbecome
password, the README recommends to run ansible withsudo
:This doesn't seem to be the right or required practice. For me it resulted in files in my
~/
owned by root a couple of times. Instead, we can tell ansible to ask for password with--ask-become-pass
or-K
:Also, it seems that
ansible-galaxy
does not needsudo
either:If you agree, I will throw a pull-request myself.
The text was updated successfully, but these errors were encountered: