On 28/04/14 12:24, Matt Martz wrote:
> It is possible actually.
>
> When in doubt, try it and see.
>
> However, it should not be considered something you want to do often.
>  In general, you should work on getting the module(s) added to core
> ansible.
I think there're cases where a module with no garnish does not much
sense. For example a module may need some package installed, or some
minimal configuration done.

Modules could add checks to verify the requirements are met, but there's
no pattern / facility to acomplish that afaik, and each module does it
on its own, in case it does. It would be easier to provide companion
roles or plays in ansible core, that need to be run before a module can
be used. Those roles/plays should be overridable to allow for
customizations.


my 2 ¢

>
>
> On Monday, April 28, 2014, Petros Moisiadis <ernes...@yahoo.gr
> <mailto:ernes...@yahoo.gr>> wrote:
>
>     Hello,
>
>     I know about a ./library path that can exist at the playbook
>     level, but
>     I did not find any reference to a ./library path at role level. Is
>     there
>     any reason why this is not supported? Would it be a desirable feature?
>     It seems to be the most sensible way to allow distribution of ansible
>     modules along with roles. The use case is that you write a role along
>     with some special modules needed for that role and want to distribute
>     your role with all needed pieces included.
>
>     --
>     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 ansible-project+unsubscr...@googlegroups.com
>     <javascript:;>.
>     To post to this group, send email to
>     ansible-project@googlegroups.com <javascript:;>.
>     To view this discussion on the web visit
>     
> https://groups.google.com/d/msgid/ansible-project/535E25E0.4040106%40yahoo.gr.
>     For more options, visit https://groups.google.com/d/optout.
>
>
>
> -- 
> Matt Martz
> m...@sivel.net <mailto:m...@sivel.net>
> http://sivel.net/
> -- 
> 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 ansible-project+unsubscr...@googlegroups.com
> <mailto:ansible-project+unsubscr...@googlegroups.com>.
> To post to this group, send email to ansible-project@googlegroups.com
> <mailto:ansible-project@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CAD8N0v94cyfGbAg594mjE9TuBTMx3e9X6xio9CAqQ0Ut518v8w%40mail.gmail.com
> <https://groups.google.com/d/msgid/ansible-project/CAD8N0v94cyfGbAg594mjE9TuBTMx3e9X6xio9CAqQ0Ut518v8w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/5360ECE1.40304%40faita.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to