-
-
Notifications
You must be signed in to change notification settings - Fork 995
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support unified requirements.yml for galaxy collections #1240
base: develop
Are you sure you want to change the base?
Support unified requirements.yml for galaxy collections #1240
Conversation
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: semaphoreui#1144
@fiftin Anything stopping this from being code-reviewed/merged? |
I'm here :) I reviewing. |
is this still a thing? |
@rwaffen As it hasn't been merged yet, I don't think it's resolved. |
it's a pitty. but how do you handle this as long this is not merged, is there a workaround for this? |
@rwaffen defining two requirement-files is the way to go and working (in 2.8.90, tested again with latest version 2.9.4): minimal example for collections:
requirements are cached and only refreshed if file(s) are changed: "roles/requirements.yml has no changes. Skip galaxy install process.". |
any updates on getting this pr merged? @stefanux can help testing if needed |
@fiftin any update on that one? |
Any Updates? |
Hi, |
@steadfasterX , @corincorvus could you please check this in latest release? |
This changeset provides support to find
ansible-galaxy
collectionrequirements.yml
relative to repo path, in thecollections/
directory. This supports inventory organisations where only one requirements.yml is set up for the entire repo.This partially resolves issues reported here: #1144