Issue #8379
open
pulp_installer depends on unsupported community collections
Description
It has come to the attention of the Ansible Platform team that pulp_installer, which we use to install Hub as part of the platform, depends on community.general, but Platform cannot depend on community collections. We can only depend on supported, official ansible-namespace content.
The current blocker is ini_file from community.general. There may be others.
Ideally, we could get these dependencies moved into a supported collection, ansible.utils, and pulp_installer could depend on that, instead.
Related issues
Updated by mdepaulo@redhat.com almost 4 years ago
- Assignee set to mdepaulo@redhat.com
Updated by kdelee@redhat.com almost 4 years ago
We also found that the installer relies on https://docs.ansible.com/ansible/latest/collections/community/general/seport_module.html
Fabricio asked if we have any tooling for scanning a collection for what modules it uses and what collections those modules are in
While it is unofficial, Alan from the tower team did create https://github.com/AlanCoding/ansible-locate so that may be useful in finding any other "invisible" dependencies on a static basis
Updated by fao89 over 3 years ago
I mapped the dependencies here: https://github.com/pulp/pulp_installer/pull/562
Updated by fao89 over 3 years ago
- Related to Story #8491: As a user I only download needed collections dependencies added
Updated by mdepaulo@redhat.com over 3 years ago
- Triaged changed from No to Yes
I will look into what the options are for dependency management on Ansible.
.