mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
document new 'order' keyword for plays
This commit is contained in:
parent
1e1caaad06
commit
70b2ceebe5
1 changed files with 25 additions and 0 deletions
|
@ -229,6 +229,31 @@ Just `Control-C` to kill it and run it again adding the appropriate password.
|
|||
not come into play. Ansible also takes care to not log password
|
||||
parameters.
|
||||
|
||||
|
||||
.. _version_added: 2.4
|
||||
.. _order:
|
||||
You can also control the order in which hosts are run, the default is to follow the order supplied by the inventory::
|
||||
|
||||
- hosts: all
|
||||
order: sorted
|
||||
gather_facts: False
|
||||
tasks:
|
||||
- debug: var=inventory_hostname
|
||||
|
||||
Possible values for order are:
|
||||
|
||||
inventory:
|
||||
The default, the order is 'as provided' by the inventory
|
||||
reverse_inventory:
|
||||
As the name implies, this reverses the order 'as provided' by the inventory
|
||||
sorted:
|
||||
Hosts are albhabetically sorted by name
|
||||
reverse_sorted:
|
||||
Reverse alphabetic ordered
|
||||
shuffle:
|
||||
Hosts are randomly ordered each run
|
||||
|
||||
|
||||
.. _tasks_list:
|
||||
|
||||
Tasks list
|
||||
|
|
Loading…
Reference in a new issue