Current development (future 2.3) add a 'user defined module_utils' feature that will allow you to ship the library with the module in the same way Ansible's module_util currently works.
On Tue, Jan 31, 2017 at 5:53 PM, Julien Buonocore <[email protected]> wrote: > Hello, > > As part of the deployment of an application specific to the business of my > company, I developed an Ansible module in Python and I also developed a > Python library for reuse and factorization the code. A bootable playbook > installs the Python library on the managed hosts, and then the module that I > developed in Python loads this library. > > My question: is this way of organizing my developments in conformity with > the philosophy of Ansible, especially on the fact that the modules are > supposed to be standalone? > > Do you think that can be a problem later on? > > > Thanks for your feedback, > > Julien. > > -- > 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/1492f681-6658-4d4b-aff8-b6aec850199a%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- ---------- Brian Coca -- 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/CACVha7faaV4p_CsSFVM_ZSErhOb%3D-%3DJfOQCyDbnUirZ68hFHTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
