-
Notifications
You must be signed in to change notification settings - Fork 12
Configure Galaxy in Molecule #255
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'm not convinced that this change is really neccessary. It seems like the behaviour is exactly the same. My interpretation for now: First it installs the collections, then it runs again for roles. Since the both runs don't know of each other, the second issues the warning. So, since it's working as expected I'm ok with both - merging or closing. Tests seem to fail because of timeouts at Rocky Linux repos. |
|
@widhalmt where is the collections.yml file, I do not see it? Did I misunderstand the goal of this PR? Can you please clarify more? |
|
Of course. I got the name wrong. 🤦🏽 I meant the |
afeefghannam89
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks ;)
This will force Molecule to run Ansible Galaxy twice. Once for roles, once for collection. fixes NETWAYS#254
This will force Molecule to run Ansible Galaxy twice. Once for roles, once for collection.
fixes #254