mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Merge pull request #5357 from sivel/no-or-higher
Do not place (or higher) in min_ansible_version
This commit is contained in:
commit
d971a53f9e
2 changed files with 61 additions and 1 deletions
|
@ -509,7 +509,7 @@ def execute_init(args, options):
|
||||||
author = 'your name',
|
author = 'your name',
|
||||||
company = 'your company (optional)',
|
company = 'your company (optional)',
|
||||||
license = 'license (GPLv2, CC-BY, etc)',
|
license = 'license (GPLv2, CC-BY, etc)',
|
||||||
min_ansible_version = '1.2 (or higher)',
|
min_ansible_version = '1.2',
|
||||||
platforms = platform_groups,
|
platforms = platform_groups,
|
||||||
categories = categories,
|
categories = categories,
|
||||||
)
|
)
|
||||||
|
|
|
@ -318,6 +318,66 @@ That's how!
|
||||||
|
|
||||||
.. _writing_your_own_iterators:
|
.. _writing_your_own_iterators:
|
||||||
|
|
||||||
|
Using register with a loop
|
||||||
|
``````````````````````````
|
||||||
|
|
||||||
|
When using ``register`` with a loop the data strucutre placed in the variable during a loop, will contain a ``results`` attribute, that is a list of all responses from the module.
|
||||||
|
|
||||||
|
Here is an example of using ``register`` with ``with_items``
|
||||||
|
|
||||||
|
- shell: echo "{{ item }}"
|
||||||
|
with_items:
|
||||||
|
- one
|
||||||
|
- two
|
||||||
|
register: echo
|
||||||
|
|
||||||
|
This differs from the data strucutre returned when using ``register`` without a loop::
|
||||||
|
|
||||||
|
{
|
||||||
|
"changed": true,
|
||||||
|
"msg": "All items completed",
|
||||||
|
"results": [
|
||||||
|
{
|
||||||
|
"changed": true,
|
||||||
|
"cmd": "echo \"one\" ",
|
||||||
|
"delta": "0:00:00.003110",
|
||||||
|
"end": "2013-12-19 12:00:05.187153",
|
||||||
|
"invocation": {
|
||||||
|
"module_args": "echo \"one\"",
|
||||||
|
"module_name": "shell"
|
||||||
|
},
|
||||||
|
"item": "one",
|
||||||
|
"rc": 0,
|
||||||
|
"start": "2013-12-19 12:00:05.184043",
|
||||||
|
"stderr": "",
|
||||||
|
"stdout": "one"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"changed": true,
|
||||||
|
"cmd": "echo \"two\" ",
|
||||||
|
"delta": "0:00:00.002920",
|
||||||
|
"end": "2013-12-19 12:00:05.245502",
|
||||||
|
"invocation": {
|
||||||
|
"module_args": "echo \"two\"",
|
||||||
|
"module_name": "shell"
|
||||||
|
},
|
||||||
|
"item": "two",
|
||||||
|
"rc": 0,
|
||||||
|
"start": "2013-12-19 12:00:05.242582",
|
||||||
|
"stderr": "",
|
||||||
|
"stdout": "two"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
|
||||||
|
Subsequent loops over the registered variable to inspect the results may look like::
|
||||||
|
|
||||||
|
- name: Fail if return code is not 0
|
||||||
|
fail:
|
||||||
|
msg: "The command ({{ item.cmd }}) did not have a 0 return code"
|
||||||
|
when: item.rc != 0
|
||||||
|
with_items: echo.results
|
||||||
|
|
||||||
Writing Your Own Iterators
|
Writing Your Own Iterators
|
||||||
``````````````````````````
|
``````````````````````````
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue