fix: issue with variable brackets inside any string in extra_vars

[przemkalit]

What does this PR do?

I am introducing this change to resolve the bug with brackets inside the extra_vars, I didn't find any other solution for this issue.

How should this be tested?

1. Create a job template or workflow with extra_vars that contains:
   url: 'https://{{ ip }}'
2. Export the object with filetree_create.
3. The extra_vars of exported object should look like this:

extra_vars:
  "url": "https://{% raw %}{{{% endraw %} ip {% raw %}}}{% endraw %}'

Is there a relevant Issue open for this?

resolves #856

Other Relevant info, PRs, etc

N/A

[ivarmu]

Instead of adding this jinja code, I'd prefer doing like follows:

regex_replace('(^[^:]*): (.*){{', '\1: !unsafe \2{{')

This is generating the following output, which should work as well, and leaves the generated yaml file more friendly:

cat example.yaml 
---
- name: play all
  hosts: a
  gather_facts: false
  vars:
    input: !unsafe |
      variable_name: 'https://{{ ip }}'
  tasks:
    - debug:
        msg:
          - "ORIGINAL: {{ input }}"
          - |
            MODIFIED: {{ input | regex_replace('(^[^:]*): (.*){{', '\1: !unsafe \2{{') }}
...

ansible-playbook -i inventory.yaml example.yaml

PLAY [play all] ******************************************************************************************************************************************************************************************************************************

TASK [debug] *********************************************************************************************************************************************************************************************************************************
ok: [hosta] => {
    "msg": [
        "ORIGINAL: variable_name: 'https://{{ ip }}'\n",
        "MODIFIED: variable_name: !unsafe 'https://{{ ip }}'\n"
    ]
}

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

[przemkalit]

Instead of adding this jinja code, I'd prefer doing like follows:

regex_replace('(^[^:]*): (.*){{', '\1: !unsafe \2{{')

This is generating the following output, which should work as well, and leaves the generated yaml file more friendly:

cat example.yaml 
---
- name: play all
  hosts: a
  gather_facts: false
  vars:
    input: !unsafe |
      variable_name: 'https://{{ ip }}'
  tasks:
    - debug:
        msg:
          - "ORIGINAL: {{ input }}"
          - |
            MODIFIED: {{ input | regex_replace('(^[^:]*): (.*){{', '\1: !unsafe \2{{') }}
...

ansible-playbook -i inventory.yaml example.yaml

PLAY [play all] ******************************************************************************************************************************************************************************************************************************

TASK [debug] *********************************************************************************************************************************************************************************************************************************
ok: [hosta] => {
    "msg": [
        "ORIGINAL: variable_name: 'https://{{ ip }}'\n",
        "MODIFIED: variable_name: !unsafe 'https://{{ ip }}'\n"
    ]
}

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

Ok, I've pushed the change to your suggestion.

[ivarmu]

LGTM