Role / Collection issues with Galaxy dependency manager

[organicveggie]

I'm sure I'm missing something obvious, but I'm struggling to get role and collection dependencies installed with the Galaxy dependency manager. I've read and re-read the documentation multiple times, but I still can't get it to work the way I think it should. Bottom line: I can't seem to get role-file or requirements-file to work at all.

Here's what works.

molecule/default/molecule.yml

---
dependency:
  name: galaxy
driver:
  name: docker
# ...

molecule/default/collections.yml

collections:
  - name: community.docker
    version: ">=1.2.0,<2"
  - name: community.general
    version: ">=2,<3"

molecule/default/requirements.yml

---
- src: geerlingguy.repo-epel
- src: geerlingguy.pip
- src: geerlingguy.docker

That seems to match the defaults in the Role code, which sets the default value of role-file to the scenario directory plus requirements.yml, and the Collections code, which sets the default value of requirements-file to the scenario directory plus collections.yml.

However, if I set the value of role-file to anything, like foo.yml, then the molecule test fails because it can't find the required roles. I've tried paths relative to the scenario:

molecule/default/molecule.yml

dependency:
  name: galaxy
  role-file: foo.yml

or

molecule/default/molecule.yml

dependency:
  name: galaxy
  role-file: ../resources/foo.yml

I also tried paths relative to the top directory of the role:

molecule/default/molecule.yml

dependency:
  name: galaxy
  role-file: molecule/default/foo.yml

and

molecule/default/molecule.yml

dependency:
  name: galaxy
  role-file: molecule/resources/foo.yml

Nothing works. Any suggestions?

$ python --version
Python 3.8.2
$ ansible --version
ansible [core 2.12.4]
$ molecule --version
molecule 3.6.0 using python 3.8
    ansible:2.12.4
    delegated:3.6.0 from molecule
    docker:1.1.0 from molecule_docker requiring collections: community.docker>=1.9.1

[zhan9san]

Hi @organicveggie

It seems you miss the options, referring to molecule.dependency.ansible_galaxy.AnsibleGalaxy

dependency:
  name: galaxy
  options:
    ignore-certs: True
    ignore-errors: True
    role-file: requirements.yml
    requirements-file: collections.yml

Besides, molecule won't merge the requirements with default but just use the one defined in dependency.options.role-file

For your case, it can be set as below. The relative path of role-file is based on the root path of project.

dependency:
  name: galaxy
  options:
    role-file: molecule/default/foo.yml

[organicveggie]

Hahahah! Wow! I can't believe I didn't catch that. :) Thank you for not calling me an idiot!