A role seems like a very good idea.
On Mon, Dec 1, 2014 at 11:09 AM, Yvo van Beek <[email protected]> wrote: > In my playbook I have to do a few calls on RVM. > > I do these calls with the shell action by: > 1) impersonating user x (sudo_user) > 2) setting the shell to bash > 3) setting the working directory to y > 4) prefixing my shell command with "source {{rvm_script_path}} ;" > > After doing 5 RVM calls this becomes a bit repetitive. For now I've put > some of the arguments in a variable and use "args: {{rvm_arg}}", but I feel > there must be a better way. > > Should I create a module or create a role for RVM? I'm not sure if a > module would reduce much of the syntax and a role seems better suited for a > sequence of tasks? > > Note: I know that there is a RVM role on Ansible Galaxy, but it is > focussed at installing RVM, not so much on using it. > > -- > 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/ea9353c8-5a8f-4e83-ad1b-1c4996ef60a7%40googlegroups.com > . > 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%2BnsWgwv%3DvcZaRJ9V5Ps4z0CO1WSmykXwdkaKJD4J5GCNy9RyQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
