Commando plugins support

[coxley]

Does this support being able to specify Commando plugins to run, such as contrib.commando.plugins,gather_info?

Could be useful to create custom plugins you'd want to run before hand or ones you often use, and then using Ansible to initiate it much like you would with the XMLRPC service.

[jathanism]

@chepazzo
On Fri, Aug 21, 2015 at 17:43 Codey Oxley [email protected] wrote:

Does this support being able to specify Commando plugins to run, such as
contrib.commando.plugins,gather_info?

Could be useful to create custom plugins you'd want to run before hand or
ones you often use, and then using Ansible to initiate it much like you
would with the XMLRPC service.

—
Reply to this email directly or view it on GitHub
#2.

[chepazzo]

Can you describe how you would want this to work? If you give an example Ansible task (i.e. how would you want to call the module), and the expected return values (for use with debugging), I can tinker around and see what I can come up with.

In theory, yes, it is possible, even if we just added a new module to the library.

The idea, here, is to mimic what Juniper and Arista have done so that in my Ansible playbooks, my tasks would use the vendor-specific modules when available and these Trigger module otherwise.

The current module included (trigger_command) is a very basic implementation that accepts a single command and a single device. Of course, we welcome any pull requests.