Skip to content

Commit

Permalink
Be more explicit about registering with a loop (#1709) (#1717)
Browse files Browse the repository at this point in the history
(cherry picked from commit 79ae207)

Co-authored-by: Sebi <[email protected]>
  • Loading branch information
patchback[bot] and Sebiee authored Jul 25, 2024
1 parent 0db9b0a commit cf34d75
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/docsite/rst/playbook_guide/playbooks_loops.rst
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ You can register the output of a loop as a variable. For example
- "two"
register: echo

When you use ``register`` with a loop, the data structure placed in the variable will contain a ``results`` attribute that is a list of all responses from the module. This differs from the data structure returned when using ``register`` without a loop.
When you use ``register`` with a loop, the data structure placed in the variable will contain a ``results`` attribute that is a list of all responses from the module. This differs from the data structure returned when using ``register`` without a loop. The ``changed``/``failed``/``skipped`` attribute that's beside the ``results`` will represent the overall state. ``changed``/``failed`` will be `true` if at least one of the iterations triggered a change/failed, while ``skipped`` will be `true` only if all iterations were skipped.

.. code-block:: json
Expand Down

0 comments on commit cf34d75

Please sign in to comment.