add no-deps option to ansible_galaxy_install for collections

[MarkusTeufelberger]

Summary

I'd like to only have the collections and their versions that I explicitly described in requirements.yml downloaded by ansible-galaxy. There is a --no-deps switch available in ansible-galaxy collection/role install, but it is not exposed as an option by the module.

I only need this for type: collection - but it would of course be nice if it also would work of type: both or type: role is specified. Potentially there need to be 2 options to be able to install roles with and collections without dependencies for example.

Issue Type

Feature Idea

Component Name

ansible_galaxy_install

Additional Information

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• plugins/modules/packaging/language/ansible_galaxy_install.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @russoz
click here for bot help

[russoz]

Thanks for placing the ticket, @MarkusTeufelberger , will be looking into that in the next days/weeks.

[russoz]

@MarkusTeufelberger any chance you have a fairly good example handy? I would like to write a test for that case.

[felixfontein]

@russoz: how about shipping a small collection (not sure, maybe a simple galaxy.yml file is already enough?) that depends on a non-existing collection; in the tests you can build a tarball from it (ansible-galaxy collection build), and then install that tarball with --no-deps. If --no-deps works it's possible to install the collection. (Assuming the building step does not check existence of the dependencies...)