So if I'm understanding it right, synchronize module should invoke synchronize action plugin to meet DRY principle.
module synchronize.py <https://github.com/ansible/ansible-modules-core/blob/devel/files/synchronize.py> action_plugin synchronize.py <https://github.com/ansible/ansible/blob/devel/lib/ansible/runner/action_plugins/synchronize.py> W dniu czwartek, 6 listopada 2014 17:11:24 UTC+1 użytkownik J Hawkesworth napisał: > > See > > http://docs.ansible.com/intro_configuration.html#action-plugins > > In essence, action plugins provide services to modules and are used for > various things including the abilty to let different modules share logic. > Modules provide a mechanism with a defined interface. For example the > ability to copy files to a remote machine is a useful capability for lots > of modules (template, unarchive), so the action plugins let other modules > use the logic in the copy module. > > > > On Thursday, November 6, 2014 10:34:07 AM UTC, cdar z wrote: >> >> Could You help and tell me the difference between an action plugin and a >> module? Why is an action plugin 'synchronize' and a module 'synchronize' at >> the same time? Thanks. >> > -- 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 email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/4b082809-52bf-4415-a2f3-384c76b92e31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
