Serious collection requirement violation of cisco.mso: undeclared dependency on cisco.nd (which isn't part of Ansible community package)

felixfontein
Thu, 04 Jul 2024 09:29:22 +0000
Project Discussions

While working on an ansible-test extension (validate-modules: reject option/alias names equal up to casing belonging to different options by felixfontein · Pull Request #83530 · ansible/ansible · GitHub) I noticed that all modules in cisco.mso depend on the collection cisco.nd, which is neither declared as a dependency of cisco.mso (ansible-mso/galaxy.yml at master · CiscoDevNet/ansible-mso · GitHub) or is part of the Ansible community package (but cisco.mso is part of it).

This basically makes it impossible to use any module of this collection when installing the Ansible community collection without manually also installing cisco.nd.

This is a clear and serious violation of Ansible community package collections requirements — Ansible Community Documentation.

I’ve created an issue in the collection’s repo: Collection does not declare its dependency cisco.nd, which also is not part of the Ansible community distribution · Issue #479 · CiscoDevNet/ansible-mso · GitHub

@SteeringCommittee how should we proceed here?

14 posts - 7 participants