mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-08-22 14:01:42 -07:00
documented new tag behaviour
This commit is contained in:
parent
65c08d1364
commit
af573db47a
1 changed files with 25 additions and 3 deletions
|
@ -40,6 +40,28 @@ And you may also tag basic include statements::
|
|||
|
||||
Both of these have the function of tagging every single task inside the include statement.
|
||||
|
||||
|
||||
Special Tags
|
||||
````````````
|
||||
|
||||
There is a special 'always' tag that will always run a task, unless specifically skipped (--skip-tags always)
|
||||
|
||||
Example::
|
||||
|
||||
tasks:
|
||||
|
||||
- debug: msg="Always runs"
|
||||
tags:
|
||||
- always
|
||||
|
||||
- debug: msg="runs when you use tag1"
|
||||
tags:
|
||||
- tag1
|
||||
|
||||
There are another 3 special keywords for tags, 'tagged', 'untagged' and 'all', which run only tagged, only untagged
|
||||
and all tasks respectively. By default ansible runs as if --tags all had been specified.
|
||||
|
||||
|
||||
.. seealso::
|
||||
|
||||
:doc:`playbooks`
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue