They will be shortly :) The short answer to that is: we decided that all plugins would live with the main code base, so that's where action plugins ended up.
James Cammarata Ansible Lead/Sr. Principal Software Engineer Ansible by Red Hat twitter: @thejimic, github: jimi-c On Wed, Aug 17, 2016 at 10:47 AM, Dusty Mabe <[email protected]> wrote: > > > On 08/17/2016 11:38 AM, James Cammarata wrote: > > Action plugins are a layer that sits between the Ansible controller and > the remote node. Typically, action plugins are used to do something on the > controller side before (or instead of) doing something on the remote side. > > > > If the bug is in the action plugin, open an issue/PR in ansible/ansible, > otherwise open it for the module in ansible/ansible-core-modules. > > > > James Cammarata > > Thanks for the explanation. > > If the two things are dependent then why not have the action plugin for > unarchive > live in the same repo as the module it corresponds to? Would it not be > safer to > have them live together in the same repo? > > If it is truly a plugin then it should be able to be provided from > anywhere so > it shouldn't need to live in ansible/ansible right? > > Dusty > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
