9 Commits (53db51a0a2c842edafb9125f061967ad71c358c5)

Author	SHA1	Message	Date
Michael DeHaan	d1ac527fb1	Add note about new logging feature in example plugin.	12 years ago
Michael DeHaan	53ac0bbec2	Instantiate callback plugins only once so we can set play/task objects on them and they'll stick.	12 years ago
Daniel Hokka Zakrisson	f12dbd431a	Don't remove invocation from the result in the log callback ... Fixes #2064.	12 years ago
Rodney Quillo	395093e0bf	Move default arguments to the end of the function call.	12 years ago
Rodney Quillo	7ae100611c	Adding default on vars_prompt	12 years ago
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	12 years ago
Dag Wieers	de34c7c133	This should set the sender properly.	12 years ago
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...	12 years ago
Michael DeHaan	41dd4a1f93	Merge plugins tree	12 years ago