mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-25 14:20:22 -07:00
Mutually reference Windows and non-Windows modules (#25482)
* Mutually reference Windows and non-Windows modules To make it easier for Windows or non-Windows users to find the relevant module information, we are mutually referencing both variants in their documentation. We are also adding a special note if a module works on both Windows and non-Windows targets. * Mutually reference Windows and non-Windows modules To make it easier for Windows or non-Windows users to find the relevant module information, we are mutually referencing both variants in their documentation. We are also adding a special note if a module works on both Windows and non-Windows targets. * Replace 'look at' with 'use', as requested ci_complete
This commit is contained in:
parent
8765eadb30
commit
7d7051fc54
50 changed files with 137 additions and 20 deletions
|
@ -26,6 +26,7 @@ description:
|
|||
- Static includes are not subject to most directives, for example, loops or conditionals, they are applied instead to each inherited task.
|
||||
- Since 2.0 task includes are dynamic and behave more like real tasks. This means they can be looped, skipped and use variables from any source.
|
||||
Ansible tries to auto detect this, use the `static` directive (new in 2.1) to bypass autodetection.
|
||||
- This module is also supported for Windows targets.
|
||||
version_added: "0.6"
|
||||
options:
|
||||
free-form:
|
||||
|
@ -34,6 +35,7 @@ options:
|
|||
notes:
|
||||
- This is really not a module, though it appears as such, this is a feature of the Ansible Engine, as such it cannot be overridden the same way a
|
||||
module can.
|
||||
- This module is also supported for Windows targets.
|
||||
'''
|
||||
|
||||
EXAMPLES = """
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue