From 6922a18c80c2038c43962daa67b2a6f5c36491df Mon Sep 17 00:00:00 2001 From: Laurens Vanderhoven Date: Thu, 22 Jun 2017 08:01:41 +0200 Subject: [PATCH] Update playbook_best_practices.rst, range notation (#25959) Update --limit range notation. Current notation triggers "[WARNING]: Use [x:y] inclusive subscripts instead of [x-y] which has been removed" --- docs/docsite/rst/playbooks_best_practices.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/playbooks_best_practices.rst b/docs/docsite/rst/playbooks_best_practices.rst index 32f45fa8d0d..edb70b5a56f 100644 --- a/docs/docsite/rst/playbooks_best_practices.rst +++ b/docs/docsite/rst/playbooks_best_practices.rst @@ -296,8 +296,8 @@ What about just my webservers in Boston?:: What about just the first 10, and then the next 10?:: - ansible-playbook -i production webservers.yml --limit boston[1-10] - ansible-playbook -i production webservers.yml --limit boston[11-20] + ansible-playbook -i production webservers.yml --limit boston[1:10] + ansible-playbook -i production webservers.yml --limit boston[11:20] And of course just basic ad-hoc stuff is also possible.::