Technically a playbook callback might be able to use low level methods inside Playbook code to run some extra tasks before things are done (MAYBE), but it's not really a supported thing and those signatures are going to change under you.
So you're stuck with wet and slippery, I'm afraid :) On Sun, Mar 23, 2014 at 7:40 PM, <[email protected]> wrote: > Thanks Michael. > We chose the second option so far, I hoped there was a way to DRY it up. > > > *For the record, you're one of the most efficient OSS maintainer I ever > saw. Kudos.* > *(and Ansible rocks)* > > On Monday, March 24, 2014 10:34:30 AM UTC+11, Michael DeHaan wrote: > >> Ansible callbacks that read events do not have the ability to insert >> other events to be run. >> >> You can solve this in two ways, always include that role last in the list >> of roles for each group, or have your playbooks end in a play that applies >> that role to *all* hosts. >> >> --Michael >> >> >> On Sun, Mar 23, 2014 at 7:27 PM, <[email protected]> wrote: >> >>> Hi List. >>> >>> >>> We have a set of tasks in a role that we'd like to be run last on every >>> single host, each time. >>> It seems like a job for a callback. >>> >>> Before I dive into it, is it possible for a callback to run a role (the >>> after playbook callback) or a whole playbook (the after run success >>> callback). >>> All the examples show local action. Is that because of a limitation or >>> just because an example never came up or did I just miss it ? >>> >>> Bonus point for pointing me in the direction :) >>> >>> Thanks. >>> raphael. >>> >>> -- >>> 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/26bf876e-5b88-47d8-9fe1- >>> 1e11ad399c32%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/26bf876e-5b88-47d8-9fe1-1e11ad399c32%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/1869cb40-f19c-4590-849a-16c3200c8453%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/1869cb40-f19c-4590-849a-16c3200c8453%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/CAEVJ8QOcAn5dSEFscVopgn0oH3MihFeY1MYr6EQ8h0vvijG-uQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
