[Moep90]

Summary

The omegaconf page now says, in a warning box, that \${...} is not a literal escape in this backend and that ${VAR:-default} in a script has to be written as ${escape:VAR:-default}. The literal output section gets a multi-line script example.

Motivation

A shell script or Helm template kept in an inventory value often contains ${VAR:-default}. In the omegaconf backend both the plain and the backslash-escaped form are resolved, the escaped one in the second pass, so the compile fails with Unsupported interpolation type VAR. Getting a literal through backslashes takes seven of them. ${escape:VAR:-default} already works, but the page only mentioned it in one sentence. This PR changes no behaviour.

Affected files or URLs

• docs/pages/inventory/omegaconf.md: the sentence below the double-pass description becomes a warning with the ${escape:VAR:-default} example and a link to the literal output section, which gets a multi-line script example and its result.
• tests/test_omegaconf.py: test_escape_resolver_keeps_shell_parameter_expansion_literal renders the docs example through the backend. The docs build has no doctests, so this test keeps the example honest.

Test plan

• Test added. It passes on master too, because it covers existing behaviour.
• Documentation updated, mkdocs build --strict passes and the new anchor link resolves
• make lint passes
• make format passes (no formatting changes needed)
• Full test suite passes (uv run pytest tests/ --no-cov)

Risk assessment

Docs and one test only.

Follow-up work intentionally left out

#1634 rewrites the deferred evaluation section and already points to ${escape:...} there. I kept this PR out of that section so the two don't conflict.

I made this change with Claude Code.