You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/man/man1/ansible.1
+13-1
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,19 @@ Connection type to use\&. Possible options are
140
140
.RE
141
141
.SH "INVENTORY"
142
142
.sp
143
-
Ansible stores the hosts it can potentially operate on in an inventory file\&. The syntax is one host per line\&. Groups headers are allowed and are included on their own line, enclosed in square brackets\&.
143
+
Ansible stores the hosts it can potentially operate on in an inventory
144
+
file\&. The syntax is one host per line\&. Optionally, ansible can use a
145
+
line of the form base[beg:end]tail to define a set of hosts, where
146
+
[beg:end] defines a numerical range. If 'beg' is left out, it
147
+
defaults to 0\&. An example: mail[1:6].example.com, where 'head'
148
+
is 'mail', 'beg' is 1, 'end' is 6, and 'tail' is '.example.com'\&. In
149
+
addition, 'beg' can be a a string padded with zero(s) to the left. If so
150
+
provided, it acts as a formatting hint during hostname expansion. The usage
151
+
must be confirmed by having an 'end' that has the same length as 'beg',
152
+
else an exception is raised. An example: mail[001:003].example.com is to be
153
+
expanded to mail001.example.com, mail002.example.com, and
154
+
mail003.example.com\&. Groups headers are allowed and are included on their
0 commit comments