From c8ef9d6d874da784b3e1de7bce300f37f92292c1 Mon Sep 17 00:00:00 2001 From: sirkubax Date: Fri, 27 Oct 2017 15:08:30 +0200 Subject: [PATCH] update --- .ansible.html.markdown.swl | Bin 36864 -> 36864 bytes ansible.html.markdown | 10 ++++++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/.ansible.html.markdown.swl b/.ansible.html.markdown.swl index d3239470ff2cd18e0048c5c13aeb8cd66ea0ab9e..259fc5a0fdcabe28f06489c96d067f9afa3a24f2 100644 GIT binary patch delta 374 zcmZozz|^pSNg>G~%+puFT+f672m}}yPUwG*EL9O=(9vUH$SzGvoVZbCqYIA!W7g(C zfzA57^~?+m&a4onS(^nNycyHpvNJHe0pi6#90$a)KjXxHoXp}9 z-IB!gVug}?Fh?P=EHN`DF)1fi0VF)x!rf6v0SFRv$`dP#89>aCjMSo3g+w4OE=Wzz zOw0kRv{GOI$xdd>mYICYO;n@=BKW%~QzF%c%tMKt`pfrYIDp7U!21C8ri|_V(E74ghHdV@?17 delta 274 zcmZozz|^pSNg>G~%+puFT+f672m}}y6!kwx3abb)=;$#pWS1r-PTZ)n(S=8VF=KO} zz-E2kPs|Jq>sTR5Gd2r4cr!){aWF6l0`X&Z28NkHJOhYJfw%yOErHkqh;@PZ6B`4= zM<8Ae#H)aK5)jt_aWW9Q0I@R=n*y;35U&SXv2OE0$7be<2g*0QxK3c4{M*fHvWvR} zTVhUmVrB7UJ2!KulEn041t8(510v(|OEOZ67!-gYGQU(IIWbQGD3GU+lbM@Yq5$Nj kR-`7EmSpDVDI`@Ylon^^r7KK+?QX%Wr>D2s+heOc053;HHUIzs 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