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
Test ansible 2.10 #448
Test ansible 2.10 #448
Conversation
|
WARNING!!! This PR is not attached to an issue. In most cases this is not advisable. Please see our PR docs for more information about how to attach this PR to an issue. |
5f08e5e
to
8a60c26
Compare
a9913bf
to
f90528a
Compare
| @@ -1,7 +1,7 @@ | |||
| --- | |||
| dependency: | |||
| name: galaxy | |||
| role-file: requirements.yml | |||
| requirements-file: requirements.yml | |||
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.
given my observation, this will not work with the last version of molecule released for python2.
c2c6f33
to
192a20e
Compare
molecule/source-upgrade/molecule.yml
Outdated
| @@ -1,7 +1,7 @@ | |||
| --- | |||
| dependency: | |||
| name: galaxy | |||
| role-file: requirements.yml | |||
| requirements-file: requirements.yml | |||
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.
I believe those lines do not effect anything there can you try removing them?
In the docs they are found beneath options:
https://molecule.readthedocs.io/en/stable/configuration.html#ansible-galaxy
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.
it is being used at dependency test: https://github.com/pulp/pulp_installer/runs/1162604142?check_suite_focus=true#step:9:28
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.
the requirements.yml is read, because this is the default value of the dependency class in molecule.
Line 4 of this file is actually ignored, because it should have been:
options:
requirements-file: requirements.yml
which will then be interpreted right in modern molecule, but call ansible-galaxy install -r requirements.yml --requirements-file requirements.yml on py2's molecule and rightfully fail with "I don't understand that parameter".
It's a mess and it took me some time to see what's going wrong.
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.
you are right, requirements-file does not work, only works with roles-file which does not install the collection
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.
And to add to the confusion, on ansible 2.10 is does install the collections in requirements.
|
I don't know what i should say with this. It is (at least in parts) green, because it doesn't work properly.
It only "works", because for anything but ansible 2.10 the collection installation is not needed. |
5dcfa96
to
2d5d879
Compare
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.
Left a few nit picky comments. What would it take to get this out of draft?
| @@ -1,7 +1,8 @@ | |||
| --- | |||
| dependency: | |||
| name: galaxy | |||
| role-file: requirements.yml | |||
| options: | |||
| role-file: requirements.yml | |||
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.
As that is molecules default, it should be ok to drop this altogether.
| - lint | ||
| - dependency | ||
| - lint |
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.
Is this change needed?
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.
yes and no.
No - as we are installing the collection at tox.ini
Yes - if we were using the molecule to install the collection, lint would break because it wouldn't recognize the collection fqdn.
As I started the PR counting on molecule, I did this change, but now we don't need it anymore
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.
"Yes and no" sounds like the theme of this PR...
Let's keep it that way, since a user can run this with molecule py3 and ansible 2.10 without the need to install collections by hand.
actually, it was in draft when I was studying molecule, and I forgot to move it back |
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.
I like this, and i am going to LGTM on it, but i'd like to see a second ACK on dropping ansible 2.8 tests, and therefore support.
Also we probably need a deprecation changelog here.
[noissue]
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.
Thank you! I'm glad we're now moving forward to Ansible 2.10 at the best time.
[noissue]