-
-
Notifications
You must be signed in to change notification settings - Fork 955
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 playbooks to have boolean when needed true/false and not yes or no #204
Labels
good first issue
Good for newcomers
Comments
Hey, thanks, It's definitely valid and ansible converts it to a boolean value. I am definitely a fan over booleans than strings though, |
6 tasks
Just a note that if anyone takes this on, they will also need to update the linting rules too. |
I will have a crack at this and will need some help with comment and criticism. |
balazshasprai
added a commit
to balazshasprai/k3s-ansible
that referenced
this issue
Oct 27, 2023
6 tasks
narigondelsiglo
pushed a commit
to narigondelsiglo/techno-tim-k3s-ansible
that referenced
this issue
Nov 22, 2023
commit 9b422ce Author: Balázs Hasprai <balazs.hasprai@hbalazs.com> Date: Fri Oct 27 12:42:47 2023 +0200 Update truthy values to true/false only, techno-tim#204
timothystewart6
added a commit
that referenced
this issue
Jan 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
update playbooks to have boolean when needed true/false and not yes or no.
The text was updated successfully, but these errors were encountered: