-
Notifications
You must be signed in to change notification settings - Fork 11
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 collections #1
Comments
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
This issue is no longer marked for closure. |
@geerlingguy This playbook is a big time saver, thank you! Are you still planning on adding support for collections? That'd be really helpful. |
@binaryfire - I'm still holding onto a slim margin of hope that someday Ansible itself could have a 'freeze' file or something so you could just define a range in your requirements.yml file... but we'll see. |
Thanks a lot for this playbook! Looking forward for the collections support. |
It's bad enough this playbook can wreck a role requirements file. Let's make it so it can handle a list of collections, too.
Example
requirements.yml
that is currently slashed in half by this playbook:Straight from the docs.
The text was updated successfully, but these errors were encountered: