-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
update tasks/rubies.yml - fix bool misuse #212
Conversation
@lpaulmp what you think? |
@danochoa could you please solve the conflicts? |
@pkuczynski hold on, looks like I added a change that's not supposed to be in here |
@pkuczynski should be good to go |
Cool, thanks! One more question: in other places we are using |
74627e9
to
072f9a3
Compare
Probably a good idea. Updated for consistency. Thanks. |
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 PR works, but does not report changes. Also error handling on the detection (existing before the PR) is problematic and could fail silently.
I have suggested changes.
@danochoa let me know if this is acceptable for you!
@thbar is it good to go now? |
@danochoa could you also add an entry in the CHANGELOG, please? |
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.
Much thanks to @danochoa for this work.
I have tested on a client installation. Deletion works when requested, reports changes, and will not fail if the ruby version is already deleted.
Looks perfect to me!
@pkuczynski I just approved, I believe it's in good shape for merging! In the future (I see that there is work ongoing on the testing infrastructure at #215), we will likely be able to add a test case for that, to ensure it doesn't regress. Poke @rvm/ansible, ready to merge, but unsure who can do that at the moment (without the Travis build passing?) |
@pkuczynski can you force merge this one (I can't on my side)? It is ready and having it into |
Sure! Done! |
This fixes issues introduced by deb1d3e as described by #209. The linked commit resolved warnings about bare variables in conditionals, but ended up breaking the conditional logic by misusing the
bool
filter. Thebool
filter returnstrue
for vars set to ‘yes’, ‘on’, ‘1’, and ‘true’, and returnsfalse
otherwise, see https://docs.ansible.com/ansible/latest/user_guide/playbooks_conditionals.html.