Hi, I'm trying to figure out if I can publish a custom module, and roles that depend on it. The developing modules <https://docs.ansible.com/ansible/developing_modules.htm> docs talk about setting ANSIBLE_LIBRARY environment variable for pointing to where a module exists, and ansible.cfg's `library` <https://docs.ansible.com/ansible/intro_configuration.html#library> can set a path, and then there's the `./library` folder within a playbook. But all of those controls are at the playbook level, not at the role level.
I can't figure out how to indicate that a role depends on a particular custom module, and next, how to publish that role in a way that brings the custom module with it to e.g. Ansible Galaxy. I see that roles can express dependencies on other roles -- which would be great, I could write a "wrapper" role around the module so it could function as a role dependency -- but I'd have to first get the module to ship with the role. Is there any way to ship a module along with a role? Or short of that, some way to declare a remote module dependency within a role? Or am I stuck with requiring every playbook that uses a role with a custom module dependency to micromanage the paths to those libraries? best, Charlie -- 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/8ca99455-47ae-4bd4-93c2-2125ac484e75%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
