How Exactly Does Ansible Parse Boolean Variables?
Variables defined in YAML files (playbooks, vars_files, YAML-format inventories)
YAML principles
Playbooks, vars_files, and inventory files written in YAML are processed by a YAML parser first. It allows several aliases for values which will be stored as Boolean
type: yes
/no
, true
/false
, on
/off
, defined in several cases: true
/True
/TRUE
(thus they are not truly case-insensitive).
YAML definition specifies possible values as:
y|Y|yes|Yes|YES|n|N|no|No|NO |true|True|TRUE|false|False|FALSE |on|On|ON|off|Off|OFF
You can also specify a boolean value (true/false) in several forms:
create_key: yes needs_agent: no knows_oop: True likes_emacs: TRUE uses_cvs: false
Variables defined in INI-format inventory files
Python principles
When Ansible reads an INI-format inventory, it processes the variables using Python built-in types:
Values passed in using the
key=value
syntax are interpreted as Python literal structure (strings, numbers, tuples, lists, dicts, booleans, None), alternatively as string. For examplevar=FALSE
would create a string equal toFALSE
.
If the value specified matches string True
or False
(starting with a capital letter) the type is set to Boolean, otherwise it is treated as string (unless it matches another type).
Variables defined through --extra_vars
CLI parameter
All strings
All variables passed as extra-vars in CLI are of string type.
dokaspar
Updated on July 27, 2022Comments
-
dokaspar almost 2 years
In Ansible, there are several places where variables can be defined: in the inventory, in a playbook, in variable files, etc. Can anyone explain the following observations that I have made?
- When defining a Boolean variable in an inventory, it MUST be capitalized (i.e., True/False), otherwise (i.e., true/false) it will not be interpreted as a Boolean but as a String.
- In any of the YAML formatted files (playbooks, roles, etc.) both True/False and true/false are interpreted as Booleans.
For example, I defined two variables in an inventory:
abc=false xyz=False
And when debugging the type of these variables inside a role...
- debug: msg: "abc={{ abc | type_debug }} xyz={{ xyz | type_debug }}"
... then
abc
becomesunicode
butxyz
is interpreted as abool
:ok: [localhost] => { "msg": "abc=unicode xyz=bool" }
However, when defining the same variables in a playbook, like this:
vars: abc: false xyz: False
... then both variables are recognized as
bool
.I had to realize this the hard way after executing a playbook on production, running something that should not have run because of a variable set to 'false' instead of 'False' in an inventory. Thus, I'd really like to find a clear answer about how Ansible understands Booleans and how it depends on where/how the variable is defined. Should I simply always use capitalized True/False to be on the safe side? Is it valid to say that booleans in YAML files (with format
key: value
) are case-insensitive, while in properties files (with formatkey=value
) they are case-sensitive? Any deeper insights would be highly appreciated. -
dokaspar over 6 yearsThanks a lot for the detailed answer. It really helped a lot. But still it lead me to yet another confusion: What causes Ansible to evaluate 'false and true' as 'true'?
-
JonnyJD almost 6 yearsgreat answer and this explains what to do to force variables as boolean anyways: stackoverflow.com/a/37895365/1904815 (use the
bool
filter) -
Xiong Chiamiov over 4 yearsYou can also pass variables as json to force them to be interpreted as booleans without needing to change your playbooks.
-
bbaassssiiee over 2 yearsNotice that the YAML parser on S.O. deviates from Ansible.
-
Todd Lewis about 2 yearsWhile true, extra-vars in Tower/AWX jobs are not from the CLI; they really are YAML (well, the YAML ones are) and thus are subject to the same parsing/processing as other YAML vars. So for booleans, not all extra-vars are strings. Only the CLI ones.