From cf34d75f5921ed4fcaa1dae4fa2eec6e5a8aeecb Mon Sep 17 00:00:00 2001 From: "patchback[bot]" <45432694+patchback[bot]@users.noreply.github.com> Date: Thu, 25 Jul 2024 17:23:26 -0400 Subject: [PATCH] Be more explicit about registering with a loop (#1709) (#1717) (cherry picked from commit 79ae2075bf950a768ed5aaea2cdf28b6dd2436ed) Co-authored-by: Sebi --- docs/docsite/rst/playbook_guide/playbooks_loops.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/playbook_guide/playbooks_loops.rst b/docs/docsite/rst/playbook_guide/playbooks_loops.rst index 27f1d120fea..7c6fb9dac6f 100644 --- a/docs/docsite/rst/playbook_guide/playbooks_loops.rst +++ b/docs/docsite/rst/playbook_guide/playbooks_loops.rst @@ -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