9 commits

Author	SHA1	Message	Date
Michael DeHaan	d1ac527fb1	Add note about new logging feature in example plugin.	2013-04-27 10:36:37 -04:00
Michael DeHaan	53ac0bbec2	Instantiate callback plugins only once so we can set play/task objects on them and they'll stick.	2013-04-20 09:09:35 -04:00
Daniel Hokka Zakrisson	f12dbd431a	Don't remove invocation from the result in the log callback ... Fixes #2064.	2013-02-12 22:26:30 +01:00
Rodney Quillo	395093e0bf	Move default arguments to the end of the function call.	2013-01-19 08:34:47 +08:00
Rodney Quillo	7ae100611c	Adding default on vars_prompt	2013-01-18 19:00:57 +08:00
Dag Wieers	8323a03fa1	Improve the mail callback to support differing failures ... Since callbacks are called with different argument-types, we have to be careful. We support two different distinct cases: - The error information can be in one ore more of the following items (msg, stderr or stdout) - The res/msg value returned can be a string or a list	2012-11-06 14:28:38 +01:00
Dag Wieers	de34c7c133	This should set the sender properly.	2012-10-12 20:40:06 +02:00
Dag Wieers	bb58d3f20c	Example plugin to send out mails on error ... This is useful mostly for playbooks that run unattended and for a limited set of systems. In case of provisioninging this plugin (together with a final mail action) helps to get notified when something went wrong, or when the installation finished successfully. Unfortunately, there is no way to enable/disable a plugin from a playbook. So installing the plugin means all other use-cases (provisioning, troubleshooting, reporting or management) all send mails on failure. Something we may want to fix in the future...	2012-10-10 17:28:00 +02:00
Michael DeHaan	41dd4a1f93	Merge plugins tree	2012-10-08 07:45:25 -04:00