"Would I need to set sudo=no on the playbook, and then sudo=yes on each task that needs it?"
This is quite reasonable. (sudo: no, not sudo=no, BTW) On Fri, Apr 25, 2014 at 12:31 PM, Adam Morris <[email protected]> wrote: > > The simple solution is not not put sudo=anything in the playbook. Those > users needing to run with sudo can use command line flags to turn that on... > > It sounds like you have two separate sets of tasks... So why not use a > pair of roles? > > If you have split your playbooks up into individual tasks you can include > some or all of them into separate playbooks. > > I have several different roles and some top level playbooks that include > some but not others... I hope that this helps. > > Adam > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/8cf097fd-9560-45e1-b468-84f0badbb0b9%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/8cf097fd-9560-45e1-b468-84f0badbb0b9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgz0NPka_ye6TC8UE%3DqG-s9RGPFg9B4i-Xpxami5yt8QmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
