Yes, you can achieve your desired output, though Jinja2 (the templating engine Ansible uses) does not support nested {% raw %} blocks directly. Instead, you can output the literal {% raw %} and {% endraw %} tags using Jinja's expression syntax, which lets you pass those tags through to your downstream system unprocessed.

Solution 1: Directly output literal tags via expressions #

Instead of trying to nest raw blocks, write the raw tags as string literals inside Jinja expressions. For your example, your Ansible template would look like this:

foobar, {{ '{% raw %}' }} 需保留此原始内容（raw块在外层） {{ '{% endraw %}' }}

When Ansible renders this template, it will replace the expressions with the literal tag strings, resulting in exactly the output you want:

foobar, {% raw %} 需保留此原始内容（raw块在外层） {% endraw %}

Solution 2: Use variables for cleaner reuse #

If you need to include these raw tags multiple times in your template, define variables for them first to avoid repeating the string literals:

{% set raw_open = '{% raw %}' %}
{% set raw_close = '{% endraw %}' %}

foobar, {{ raw_open }} 需保留此原始内容（raw块在外层） {{ raw_close }}

This produces the same output as the first solution but is more maintainable for larger templates.

Why nested raw blocks don't work #

Jinja2 treats the first {% endraw %} it encounters as the closing tag for the outermost {% raw %} block. So if you tried writing:

{% raw %} foobar, {% raw %} 需保留此原始内容（raw块在外层） {% endraw %} {% endraw %}

Ansible would throw an error because the second {% endraw %} has no matching opening {% raw %} block (the first {% endraw %} already closed the outer one).

So while you can't nest raw blocks, the expression-based approach effectively lets you "escape" the raw tags themselves for your downstream system.

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