From 5bba9180522cc2866ee9e5de72540cdb6716fe4d Mon Sep 17 00:00:00 2001 From: Aaron Mortenson Date: Thu, 9 Jun 2016 13:13:51 -0400 Subject: [PATCH] added more documentation of loops with register (#16208) --- docsite/rst/playbooks_variables.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index 8cd5e8443c6..57b68a96705 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: