MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide #1283
Conversation
ansible-documentation-bot
bot
added
the
new_contributor
|
Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda. |
Devids10
changed the title
| @@ -154,22 +154,24 @@ In a playbook, you can set module defaults for whole groups of modules, such as | |||
|
|
|||
| In ansible-core 2.12, collections can define their own groups in the ``meta/runtime.yml`` file. ``module_defaults`` does not take the ``collections`` keyword into account, so the fully qualified group name must be used for new groups in ``module_defaults``. | |||
|
|
|||
| Here is an example ``runtime.yml`` file for a collection and a sample playbook using the group. | |||
| Here is an example ``runtime.yml`` file for the ``ns.coll`` collection defining an action group ``ns.coll.my_group`` and placing the ``sample_module`` from ``ns.coll`` and ``another_module`` from ``another.collection`` into it. | |||
There was a problem hiding this comment.
| Here is an example ``runtime.yml`` file for the ``ns.coll`` collection defining an action group ``ns.coll.my_group`` and placing the ``sample_module`` from ``ns.coll`` and ``another_module`` from ``another.collection`` into it. | |
| Here is an example ``runtime.yml`` file for the ``ns.coll`` collection. | |
| This file defines an action group named ``ns.coll.my_group`` and places the ``sample_module`` from ``ns.coll`` and ``another_module`` from ``another.collection`` into the group. |
oraNod
added
backport-2.16
Backport to stable-2.15: 💚 backport PR created✅ Backport PR branch: Backported as #1336 🤖 @patchback |
MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide (cherry picked from commit 87886f1)
Backport to stable-2.14: 💚 backport PR created✅ Backport PR branch: Backported as #1337 🤖 @patchback |
MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide (cherry picked from commit 87886f1)
Backport to stable-2.16: 💚 backport PR created✅ Backport PR branch: Backported as #1338 🤖 @patchback |
MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide (cherry picked from commit 87886f1)
Backport to stable-2.17: 💚 backport PR created✅ Backport PR branch: Backported as #1339 🤖 @patchback |
MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide (cherry picked from commit 87886f1)
…/87886f18ee012b103c0bb831bf8aeaa7db591dce/pr-1283 [PR #1283/87886f18 backport][stable-2.17] MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide
…/87886f18ee012b103c0bb831bf8aeaa7db591dce/pr-1283 [PR #1283/87886f18 backport][stable-2.16] MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide
…/87886f18ee012b103c0bb831bf8aeaa7db591dce/pr-1283 [PR #1283/87886f18 backport][stable-2.14] MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide
…/87886f18ee012b103c0bb831bf8aeaa7db591dce/pr-1283 [PR #1283/87886f18 backport][stable-2.15] MUNI_TECH_WRITERS: Clarify example module group name in the playbook guide
This branch fixes the confusion in the example module group name in the issue #1070. Special thanks to @evgeni for the new clear example.