-
-
Notifications
You must be signed in to change notification settings - Fork 127
Remove meta/requirements.yml and document collection dependencies #1001
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
Conversation
I noticed the changes from my PR #990 got reverted, was this intentional? In any case, those changes no longer worked, i got
This PR is the only thing that works, not sure what's going on. For reference:
Any idea why this is not failing in CI? |
Apparently it's not supported at all? ansible/ansible#76030 Maybe get rid of it and include in the readme explicitly the collection requirements? |
no, not at all. I don't know why your PR wasn't successfully merged and the file updated. |
in what situation should it break?
|
If you use your role in a
(or probably also the published version) and then run Then you get the error, either that the structure is incorrect (roles cannot have |
But what I've read online is that it is best to point users in the readme to explicitly add these dependencies on collections themselves. Ansible apparently doesn't support this. |
i vote for removing |
Agreed! |
update the PR and I'll merge it. |
Users should install required collections themselves rather than having them auto-installed via meta dependencies. Updated README to provide clear installation instructions for ansible.posix, community.crypto, and community.general collections.
66b2fbe
to
806beb6
Compare
done |
thanks! |
No description provided.