We have a handful of “common” roles that are used by many of our Ansible projects. These projects list their required roles in their respective roles/requirements.yml files. Nothing surprising here; it’s worked this way for years.
With recent maintenance, one of these “common” roles has started using bits from a couple of collections — community.general and ansible.utils. From reading the docs, I erroneously thought I could specify those collections in meta/requirements.yml like so:
You should generally not do this. If you have content that is distributed, it should only rely on others of its type. A standalone role on a standalone role, or a collection on a collection. Note that collections can contain roles.
As such, there is no automatic installation of dependencies.
Should you wish to keep your use of standalone roles with dependencies on collections you would just have to rely on documentation. And maybe insert some form of canary test, that tries to use a module you need, wrapped in a block/rescue that then provides a friendly error when the module is not available.
Right - there is no mechanism in Ansible to do this. This is what we did for linux system roles - https://linux-system-roles.github.io/documentation/role-requirements.html - basically, made up our own file and rely on documentation.
Alas, these projects all run on AWX, so we can’t rely on documented extra steps. It needs to work using the existing AWX scm update processes.
We get away with it as long as the required collections are already installed in one of the collection path directories. And they often will be on local workstations or AWX. But we obviously can’t rely on that.
We’ll either have to move these roles into our “collection-common” project from which we build our common collection, adding the dependencies to galaxy.yml there, or we’ll need to ensure through our CI pipelines that projects pulling in the common roles include their required collections in each project’s collections/requirements.yml.
This is not at all the answer I was expecting. But at least I can quit trying to make the unworkable work.
If you are using awx, you can just create a collections/requirements.yml file that can specify those needed collections.
See: https://github.com/ansible/awx/blob/devel/docs/collections.md
This is what we do. When we know lots of different services and workflows require a given collection we add it to the AWX (Ansible Tower) controller so the projects themselves don’t have to worry about them.
Walter