Background: I'm exploring using Ansible to provision a CI master/slave set for EtE testing. I'm using Vagrant to build VMs on my local workstation.
Vagrant creates it's VMs with a default vagrant user that has SUDO privileges. The user created during a Ubuntu installation on the production machine doesn't (haven't verified this yet) So I've found certain tasks that don't require SUDO to run on the Vagrant VM do require it on the production machines. Question: Is there a favoured approach for unifying tasks that will run against both situations? - Add the same production user name account to the Vagrant image? - Add the user on the production box to SUDOERS using Ansible? - Add sudo yes to the hosts file? - Something else? -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/bc7256ba-6c4c-4b75-bab1-3278579932d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
