Skip to content

porting guide 2.19: nicer rendering for Ansible output #2877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 23, 2025
Merged

porting guide 2.19: nicer rendering for Ansible output #2877

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,7 +380,7 @@ Due to some string results previously parsing as lists, this mistake often went

The result of this template becomes a string:

.. code-block:: console
.. code-block:: ansible-output

ok: [localhost] => {
"msg": "['prod1', 'prod2']"
Expand All @@ -397,7 +397,7 @@ This can be resolved by using the ``map`` filter to apply the ``replace`` filter

The result of the corrected template remains a list:

.. code-block:: console
.. code-block:: ansible-output

ok: [localhost] => {
"msg": [
Expand Down