Skip to content
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

Merged
merged 8 commits into from
Jul 29, 2020

Conversation

danochoa
Copy link
Contributor

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. The bool filter returns true for vars set to ‘yes’, ‘on’, ‘1’, and ‘true’, and returns false otherwise, see https://docs.ansible.com/ansible/latest/user_guide/playbooks_conditionals.html.

@pkuczynski pkuczynski requested a review from lpaulmp March 31, 2020 19:16
@pkuczynski
Copy link
Member

@lpaulmp what you think?

@pkuczynski pkuczynski requested a review from a team July 21, 2020 09:41
@pkuczynski
Copy link
Member

@danochoa could you please solve the conflicts?

@danochoa
Copy link
Contributor Author

@pkuczynski hold on, looks like I added a change that's not supposed to be in here

@danochoa
Copy link
Contributor Author

@pkuczynski should be good to go

@pkuczynski
Copy link
Member

Cool, thanks! One more question: in other places we are using is defined - wouldn't it be better here too? At least for consistency reasons...

@danochoa
Copy link
Contributor Author

Probably a good idea. Updated for consistency. Thanks.

Copy link
Contributor

@thbar thbar left a 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!

tasks/rubies.yml Outdated Show resolved Hide resolved
@pkuczynski
Copy link
Member

@thbar is it good to go now?

@pkuczynski
Copy link
Member

@danochoa could you also add an entry in the CHANGELOG, please?

@pkuczynski pkuczynski added the bug label Jul 27, 2020
@thbar thbar self-requested a review July 28, 2020 10:33
thbar
thbar previously approved these changes Jul 28, 2020
Copy link
Contributor

@thbar thbar left a 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!

@thbar
Copy link
Contributor

thbar commented Jul 28, 2020

@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?)

@gildegoma
Copy link
Contributor

gildegoma commented Jul 28, 2020

@thbar Once #215 is merged, this PR (and many others) should no longer fail (the Travis CI failure reason is that the build tries to install latest Bundler version on Ruby 2.2, but Bundler 2.0+ requires Ruby >= 2.3)

@thbar
Copy link
Contributor

thbar commented Jul 29, 2020

@pkuczynski can you force merge this one (I can't on my side)? It is ready and having it into master would be useful immediately to a number of people (I will also close related issues afterwards).

@pkuczynski
Copy link
Member

Sure! Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants