Using AWX 24.6.1 and have a Workflow that has one node that finishes with a set_stats of a dictionary that contains some values that are strings with a value of “true”
In AWX we see the artifacts as string values, and in the next node of the workflow we see the extra vars with the dictionary with string values.
When the second node template runs and Ansible 2.18 is in the EE, the dictionary values contain the strings as expected
When we upgrade our EE to include Ansible 2.19 and change nothing else, this dictionary variable still shows in AWX Variables as having strings, but at execution time they have been converted to a Boolean value of true
Unfortunately, the Azure modules require that values for tags must be string, so this casting change causes the task to fail
We are temporarily getting around it by adding a new task to loop through the values and convert each to a string such as
- name: Use a Jinja loop to create a new dictionary with string values
ansible.builtin.set_fact:
stringified_vm_tags: "{{ stringified_vm_tags | default({}) | combine({item.key: item.value | string}) }}"
loop: "{{ vm_tags | dict2items }}"
Is this an intentional change or something broken with AWX? If I run from the CLI and provide the same extra_vars the strings stay as strings
Note: We had the same issue with a value that was in quotes as a string but contained only numbers and the same thing occurred where it converted it to an Int, which failed as well with the Azure modules that require that tags be strings