Extend boolean values section in playbooks_variables

[skilyazhnev]

Hello!

in continuation of this issue

#1279

[ansible-documentation-bot]

Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda.

[oraNod]

LGTM. Thanks @skilyazhnev

[ssbarnea]

I would avoid using "native boolean" for anything else than true/false because the only values that are native booleans in all versions of YAML specification.

Maybe we should mention that bit. Currently Ansible uses a YAML 1.1 loader, but when it will move to a 1.2 loader, only these values will remain booleans. This might help people understand better the long term implications.

[bcoca]

the issue is not only YAML, Ansible has internal functions to convert booleans that follow the YAML 1.1 spec, so this can apply to JSON and Jinja2.

[skilyazhnev]

I would avoid using "native boolean" for anything else than true/false because the only values that are native booleans in all versions of YAML specification.

I can change header to Recognizable as Boolean (or smth like that) for that section, to separate it from Native boolean definition in yaml 1.2

And as I see, that section of Recognizable as Boolean\Native boolean still has to to be present here for new ansible version with new loader if it will support Core Schema of yml 1.2 because there still several valid variants of inputs true | True | TRUE | false | False | FALSE.
If not (It will wotk only with Json Schema) - in new version ofk make sense to reduce it to only two values.

PS: We can add some note like: just use true\false because that easier for everyone around

[skilyazhnev]

@ssbarnea
Could u plz clarify about yaml schema and name of segment to change PR

[oraNod]

@skilyazhnev Thanks for keeping at this one.

How about we keep the "Native boolean" heading but put only true / false underneath that to reflect what @ssbarnea has mentioned about the spec: https://yaml.org/spec/1.2-old/spec.html#id2803629

For the other values in the current table, maybe we could rename the heading to "Implicit boolean"? Something like this:

Native boolean
--------------

Ansible treats these values as native booleans:

<table goes here>

Implicit boolean
------------------------

Ansible recognizes these values as booleans:

<table goes here>

[oraNod]

Let's consider giving an example here with the | bool filter.