Support unified requirements.yml for galaxy collections

[andreas-marschke]

This changeset provides support to find ansible-galaxy collection requirements.yml relative to repo path, in the collections/ directory. This supports inventory organisations where only one requirements.yml is set up for the entire repo.

This partially resolves issues reported here: #1144

[andreas-marschke]

@fiftin Anything stopping this from being code-reviewed/merged?

[fiftin]

Hi @andreas-marschke

I'm here :) I reviewing.

[rwaffen]

is this still a thing?
i'm on v2.9.16 and still having the problem that $repository/collections/requirements.yml is ignored :(

[andreas-marschke]

@rwaffen As it hasn't been merged yet, I don't think it's resolved.

[rwaffen]

it's a pitty. but how do you handle this as long this is not merged, is there a workaround for this?

[stefanux]

@rwaffen defining two requirement-files is the way to go and working (in 2.8.90, tested again with latest version 2.9.4):
roles/requirements.yml
collections/requirements.yml

minimal example for collections:

---
collections:
  - name: community.general

requirements are cached and only refreshed if file(s) are changed: "roles/requirements.yml has no changes. Skip galaxy install process.".
if you experience problems see output of semaphore and make another issue since this is a feature issue.

[RusticPotatoes]

any updates on getting this pr merged? @stefanux can help testing if needed

[steadfasterX]

@fiftin any update on that one?

[corincorvus]

Any Updates?