You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
you have the json_body inserted as json everywhere. It is possible to continue with yaml notation right away but if you insert logik with jinja2, it gets automatically converted into strings. Possibly, this is the reason why you switched to json.
If sou set DEFAULT_JINJA2_NATIVE (https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-jinja2-native) to true, you can use yaml inside the playbook for the api_body as it is intended.
So, just a small change with huge impact regarding usability for this module.
Best regards
The text was updated successfully, but these errors were encountered:
Hi everyone,
you have the json_body inserted as json everywhere. It is possible to continue with yaml notation right away but if you insert logik with jinja2, it gets automatically converted into strings. Possibly, this is the reason why you switched to json.
If sou set DEFAULT_JINJA2_NATIVE (https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-jinja2-native) to true, you can use yaml inside the playbook for the api_body as it is intended.
So, just a small change with huge impact regarding usability for this module.
Best regards
The text was updated successfully, but these errors were encountered: