ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Update playbook_best_practices.rst, range notation (#25959)

Browse source 
Update --limit range notation.

Current notation triggers "[WARNING]: Use [x:y] inclusive subscripts instead of [x-y] which has been removed"
This commit is contained in:
Laurens Vanderhoven 2017-06-22 08:01:41 +02:00 • committed by scottb
parent b2f46753ec
commit 6922a18c80
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/docsite/rst/playbooks_best_practices.rst
View file

@ -296,8 +296,8 @@ What about just my webservers in Boston?::
What about just the first 10, and then the next 10?:: 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[1:10]
ansible-playbook -i production webservers.yml --limit boston[11-20] ansible-playbook -i production webservers.yml --limit boston[11:20]
And of course just basic ad-hoc stuff is also possible.:: And of course just basic ad-hoc stuff is also possible.::