summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorsirkubax <muszynski@so1.net>2017-10-27 15:08:30 +0200
committersirkubax <muszynski@so1.net>2017-10-27 15:08:30 +0200
commitc8ef9d6d874da784b3e1de7bce300f37f92292c1 (patch)
treee558fa3d9242a8e8b6c1b6ec426cb5a27d427d39
parent147533c849733dadc2c3db31e9365ff4b4943cbe (diff)
update
-rw-r--r--.ansible.html.markdown.swlbin36864 -> 36864 bytes
-rw-r--r--ansible.html.markdown10
2 files changed, 6 insertions, 4 deletions
diff --git a/.ansible.html.markdown.swl b/.ansible.html.markdown.swl
index d3239470..259fc5a0 100644
--- a/.ansible.html.markdown.swl
+++ b/.ansible.html.markdown.swl
Binary files differ
diff --git a/ansible.html.markdown b/ansible.html.markdown
index 95735e21..0ad58d45 100644
--- a/ansible.html.markdown
+++ b/ansible.html.markdown
@@ -295,14 +295,16 @@ You can define complex logic with Ansible and Jinja functions. Most common is us
You should know about a way to increase efficiency by this simple functionality
#### TAGS
-You can tag a task, role (and its tasks), include, etc...
+You can tag a task, role (and its tasks), include, etc, and then run only the tagged resources
- You can then limit an execution by using
- ansible-playbook playbooks/simple_playbook.yml --tags tagA, tag_other
+ ansible-playbook playbooks/simple_playbook.yml --tags=tagA,tag_other
+ ansible-playbook playbooks/simple_playbook.yml -t tagA,tag_other
- There are special tags: always
+ There are special tags:
+ always
--skip-tags can be used to exclude a block of code
+ --list-tags to list available tags
#### LIMIT
You can limit an execution of your tasks to defined hosts