Hey there, let's sort out that Ansible template issue you're hitting! The root problem here is that when you use null directly in the default() filter, Ansible interprets it as an undefined variable instead of the JSON null value you actually need. Here are a couple of straightforward solutions to get the behavior you want:

Method 1: Use Jinja2 Conditionals in the Template #

You can explicitly check if the variable exists and render the correct JSON syntax on the fly:

{"value": {% if example.value is defined and example.value is not none %}"{{ example.value }}"{% else %}null{% endif %}"}

When example.value is present and not empty, this outputs a properly quoted string. When it's missing or undefined, it outputs the unquoted null (valid JSON null) that your API expects.

Method 2: Use Ansible's to_json Filter (Cleaner, Less Error-Prone) #

This approach lets Ansible handle the JSON formatting for you, avoiding manual string hacks:

1. First, set up a variable that uses none (Python's equivalent of JSON null) as the default:

   vars:
     payload_value: "{{ example.value | default(none) }}"
   

2. Then in your json.j2 template, pass that variable through the to_json filter:

   {"value": {{ payload_value | to_json }}}
   

The to_json filter does all the heavy lifting: it converts Python strings to quoted JSON strings, and Python none directly to JSON null. Perfect match for your API's requirements!

Just remember: Don't wrap the to_json output in quotes — the filter already adds quotes for string values automatically.

内容的提问来源于stack exchange，提问作者user2519653