-
Notifications
You must be signed in to change notification settings - Fork 73
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
Tasks are not being skipped based on defaults/main.yml or passing '-e taskname=false' #229
Comments
hi @mboeker Thank you for raising this issue, this is one of those things that has been going on for some time. Historically using the ini format on the command line has been inconsistent as it sets it as a string (depending how conditionals etc have been written), ansible have been trying stating it for some time although it was (a little hidden) in documentation to use json instead. [key=value format]
Values passed in using the key=value syntax are interpreted as strings. Use the JSON format if you need to pass non-string values such as Booleans, integers, floats, lists, and so on. Generally for more consistency when running playbooks any changes that are expected such as your examples, i would add to the inventory file (in yaml) or other variable location thats loaded, ensuring that nothing gets missed on subsequent runs. Being set as a default variable (the lowest type) these are easily overridden by alternative variables. I hope that helps you and others. uk-bolly |
Interesting, I've never tried passing JSON args. But that wouldn't explain why it's still running tasks when they are only defined in defaults/main.yml as false. I'll give the JSON args a shot. |
Strange you are having the problem with the defaults main also, thank you for highlighting. Have you tested devel at all, see if the issues exists there also? We skip/change a number of these during testing and they all appear to work. Will try and replicate as soon as able. |
Hi uk-bolly, I've been digging some more. Per https://stackoverflow.com/questions/39640654/using-true-false-with-ansible-when-clause as of ansible 2.8 if a variable is given as a parameter (which I assume also applies to defaults/main.yml), the condition has to be converted to |
I have not tested with devel as the playbook works once I've modified it to have |
The same info from the official source :)
|
hi @mboeker I would be happy to see what happening with your setup to be causing this. We have in excess of 70 repos setup without the | bool requirement and we've not had the feedback from others experiencing this issue. Many thanks uk-bolly |
Describe the Issue
I am trying to run the playbook with certain components skipped. For example NetworkManager, I don't want that installed. I tried both of these options:
ubtu22cis_install_network_manager: false
in defaults/main.yml, and
ansible-playbook -e ubtu22cis_install_network_manager=false site.yml
but it is still installing it. Same with rule 5.3.4, sudo password. Even when I set
ubtu22cis_rule_5_3_4: false
and pass-e ubtu22cis_rule_5_3_4=false
it sets a sudo password.Expected Behavior
Tasks get skipped if defaults/main.yml or -e args are set to false.
Actual Behavior
Tasks are still processed.
Control(s) Affected
Hardening process
Environment (please complete the following information):
Additional Notes
When I change the playbooks to explicitly check for
bool
they work as expected.So this task, in prelim.yml:
That will install network manager no matter what is set in defaults/main.yml or passed as an arg. HOWEVER, if I change the task to this, appending
| bool
to ubtu22cis_install_network_manager:then it will skip the task if I set the variable in defaults/main.yml or pass the argument.
Possible Solution
See notes.
The text was updated successfully, but these errors were encountered: