I actually started out to create a callback that triggered on change, but after some internal discussion, decided that I didn't want it to fire after each task, but rather, wanted to run it one time in the beginning and once at the end, so I figured that calling it as a task would be more appropriate.
That said, one future enhancement will be to open the ticket at the beginning, then update it after each changed task, in which case, I plan to use module tasks to create and close the ticket and then use a callback_plugin to update the ticket with results as they come in. Of course, if I've already written a module, I could set the updates to run as a handler task on change. -- 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/71e628c7-e6af-4ee8-8ff4-e52d46c047b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
