If you want greater control of when your common tasks get executed, I would be more inclined to use rules and have verbose playbooks with the execution order explicitly specified.
Perhaps if you could give a better idea of what your common tasks are and the context in which you want to run them? Regards Tom On 13 Jan 2015 16:26, <j...@ioctl.org> wrote: > On Tue, 13 Jan 2015, Brian Coca wrote: > > > no, you need to use role dependencies for that case > > > > http://docs.ansible.com/playbooks_roles.html#role-dependencies > > Ah. But tasks for role dependencies are all fired off in advance, right? > > I'm talking about having a common "subroutine" task, commonly provided > through a central point, that can be called like any other module might be > called, from an arbitrary point within a playbook. > > (The point of this is to provide some abstraction, so that client > playbooks can be written in terms of higher-level operations than the > concrete modules typically provided. Is that just a misplaced desire to > "do ansible wrong"? :-) ) > > -- > j...@ioctl.org http://ioctl.org/jan/ Short, dark, ugly: pick any three > Don't annihilate, assimilate: MacDonalds, not missiles. > -- 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/CAAnNz0PbhCbgUJ7dq-KvXrpt7RDW3unmctLBgqLOg63KxqU9GQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
