filetree_create should output yamllint compatible truthy values

[kbreit-insight]

Summary

I use the filetree_create role to extract the configuration to assist in creating data structures. Unfortunately, the output of boolean values is True or False. When I run ansible-lint or yamllint it says these are incorrect truthy values since it prefers lowercase.

Issue Type

• Bug Report

Desired Behavior

The output should be valid YAML, at least related to truthiness.

[djdanielsson]

you could just change your lint rules to allow for True/False those yamllint rules are not default

[ivarmu]

Hi @kbreit-insight. The filetree_create role is using the filter bool (see https://docs.ansible.com/ansible/latest/collections/ansible/builtin/bool_filter.html) to generate the boolean values. If there's any requirement to have that values in lowercase, I'd propose to just run some commands using sed to translate them to your needs.

[ivarmu]

I've seen an incoherent behaviour when running the bool filter:

$ cat /tmp/test.yaml             
---
- hosts: localhost
  connection: local
  vars:
    testvar: 0
  tasks:
    - debug:
        msg:
          - "{{ testvar | bool }}"
          - "{{ testvar | bool | lower }}"
    - template:
        src: /tmp/test.j2
        dest: /tmp/test.out
...
$ cat /tmp/test.j2               
{{ testvar | bool }}
{{ testvar | bool | lower }}
$ ansible-playbook /tmp/test.yaml
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [localhost] *****************************************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ***********************************************************************************************************************************************************************************************************************
ok: [localhost]

TASK [debug] *********************************************************************************************************************************************************************************************************************************
ok: [localhost] => {
    "msg": [
        false,
        "false"
    ]
}

TASK [template] ******************************************************************************************************************************************************************************************************************************
changed: [localhost]

PLAY RECAP ***********************************************************************************************************************************************************************************************************************************
localhost                  : ok=3    changed=1    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   

$ cat /tmp/test.out             
False
false
$

So... it's only written down capitalized when is used into a template (not while in debug)... It should be no such an effort modifying the templates to generate lowercase outputs... I'm working on it, as it seems more consistent with the Ansible Truthy values.