summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Mortenson <aamortenson1@gmail.com>2016-06-09 13:13:51 -0400
committerBrian Coca <bcoca@ansible.com>2016-06-09 13:13:51 -0400
commit5bba9180522cc2866ee9e5de72540cdb6716fe4d (patch)
treef69d97d6f8eb2fe527aef7c7ff7afc14c270d8ec
parente81f14ab48c89717c59df4749c674823bc7da56d (diff)
downloadansible-5bba9180522cc2866ee9e5de72540cdb6716fe4d.tar.gz
added more documentation of loops with register (#16208)
-rw-r--r--docsite/rst/playbooks_variables.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst
index 8cd5e8443c..57b68a9670 100644
--- a/docsite/rst/playbooks_variables.rst
+++ b/docsite/rst/playbooks_variables.rst
@@ -599,6 +599,8 @@ While it's mentioned elsewhere in that document too, here's a quick syntax examp
Registered variables are valid on the host the remainder of the playbook run, which is the same as the lifetime of "facts"
in Ansible. Effectively registered variables are just like facts.
+When using ``register`` with a loop the data structure placed in the variable during a loop, will contain a ``results`` attribute, that is a list of all responses from the module. For a more in-depth example of how this works, see the :doc:`playbook_loops` section on using register with a loop.
+
.. note:: If a task fails or is skipped, the variable still is registered with a failure or skipped status, the only way to avoid registering a variable is using tags.
.. _accessing_complex_variable_data: