Are any of you using nay clever tricks to parse the log file and email
output of just changed tasks back to a defined address? Id' love to be able
to know when ansible has fixed something on one or more of my boxes.
I think a callback plugin may be what you want, as you can 'trigger' on
all
On Friday, 10 January 2014 09:57:38 UTC+1, JP Mens wrote:
Dag Wieers has written something which sounds to me as though it's just
what you need [1] and there are more examples at [2].
[1]
https://github.com/ansible/ansible/blob/devel/plugins/callbacks/mail.py
[2]
Thanks for these pointers JP. The mail plugin looks interesting, and is
probably what I need. How do I call it from a playbook though?
You don't -- that's the magic. :-)
You configure Ansible to use that callback plugin by dropping into the
directory you configure for callback plugins [1].
On 10 January 2014 10:38, Jan-Piet Mens jpm...@gmail.com wrote:
that's the magic. :-)
It's not magic, it's Cow Power.
--
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
It would be nice if ansible-galaxy had support for distributing these sort
of plugins.
On Friday, January 10, 2014 9:38:38 AM UTC, JP Mens wrote:
Thanks for these pointers JP. The mail plugin looks interesting, and is
probably what I need. How do I call it from a playbook though?
You
On 10 January 2014 11:33, bryan hunt picsolvebr...@gmail.com wrote:
It would be nice if ansible-galaxy had support for distributing these sort
of plugins.
+1
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group
It doesn't make sense to include in Galaxy as callbacks are not role based.
Effectively it would just make it an index of useful things on GitHub where
already this is included in the main project.
Alternatively, what might be nice is shipping example plugins in a
directory, such that they get
