Specify Collection for Galaxy dependency

Issue Type

• Feature request

Molecule and Ansible details

ansible --version && molecule --version

ansible 2.9.1
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/artis3n/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/artis3n/.local/share/virtualenvs/dev-setup-cQlga8yo/lib/python3.7/site-packages/ansible
  executable location = /home/artis3n/.local/share/virtualenvs/dev-setup-cQlga8yo/bin/ansible
  python version = 3.7.5 (default, Nov 24 2019, 17:46:35) [GCC 9.2.1 20191008]

molecule, version 2.22

Molecule installation method (one of):

• source
• pip (pipenv)

Ansible installation method (one of):

• source
• pip (pipenv)
• OS package

Desired Behavior

dependency:
  name: galaxy
  options:
    role-file: requirements.yml
    collection-file: requirements.yml

With a requirements.yml format following https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#install-multiple-collections-with-a-requirements-file:

---

roles:
- src: gantsign.visual-studio-code
- src: artis3n.bitwarden_app

collections:
- name: artis3n.github

Molecule’s galaxy dependency doesn’t appear to support a collection-file similar to the role-file to install Galaxy Collections. I posed a question on Stack Overflow but based on the documentation I’m reasonably sure the functionality doesn’t exist yet, so posting a feature request.

[greg-hellings]

PR #2609 is up. For me, at least, it supports what I need. It does not default to using the same file as the role-file argument. Prior to collections, a requirements.yml could just be a list of roles, e.g.:

- foo.bar  # This syntax will error on "ansible-galaxy collection install"
- foo.baz
- foo.yam

To install collections with ansible-galaxy you MUST indicate a collections key with appropriate names in a list. Optionally roles can be kept in the same file

collections:  # This is required for "ansible-galaxy collection install"
  - collection.foo
  - collection.bar
roles:  # This is optional and is understood by "ansible-galaxy install"
  - foo.bar
  - foo.baz

If I pointed collections at the same requirements.yml that is used for “ansible-galaxy install” calls currently, it would detect the file and could cause existing scenarios to break unnecessarily if they do not match the newer dictionary syntax.

So the PR looks, by default, for collections.yml and can be configured with the requirements-file key in your molecule.yml.

[greg-hellings]

As an update, I have code working in my local space for this. I’m working on updating unit and functional tests to accommodate the code changes I’ve made. Expect a PR within a day or two.