Doc fixes for readability (formatting/punctuation) (#61086)

Variable-width font was extremely difficult to read in a couple places.
Fixed missing close-quote, colon, spelling, etc.
pull/61203/head
Brett Campbell 5 years ago committed by Sandra McCann
parent d31876416b
commit 5b16e012a4

@ -52,16 +52,16 @@ You can do combinations::
webservers:dbservers:&staging:!phoenix webservers:dbservers:&staging:!phoenix
The above configuration means "all machines in the groups 'webservers' and 'dbservers' are to be managed if they are in The above configuration means "all machines in the groups 'webservers' and 'dbservers' are to be managed if they are also in
the group 'staging' also, but the machines are not to be managed if they are in the group 'phoenix' ... whew! the group 'staging', but the machines are not to be managed if they are in the group 'phoenix'." Whew!
You can also use variables if you want to pass some group specifiers via the "-e" argument to ansible-playbook, but this You can also use variables if you want to pass some group specifiers via the ``-e`` argument to ansible-playbook, but this
is uncommonly used:: is uncommonly used::
webservers:!{{excluded}}:&{{required}} webservers:!{{excluded}}:&{{required}}
You also don't have to manage by strictly defined groups. Individual host names, IPs and groups, can also be referenced using You also don't have to manage by strictly defined groups. Individual host names, IPs, and groups can also be referenced using
wildcards wildcards:
.. code-block:: none .. code-block:: none
@ -88,7 +88,7 @@ You can refer to hosts within the group by adding a subscript to the group name:
webservers[1:] # == webbing,weber webservers[1:] # == webbing,weber
webservers[:3] # == cobweb,webbing,weber webservers[:3] # == cobweb,webbing,weber
Most people don't specify patterns as regular expressions, but you can. Just start the pattern with a '~':: Most people don't specify patterns as regular expressions, but you can. Just start the pattern with a ``~``::
~(web|db).*\.example\.com ~(web|db).*\.example\.com
@ -96,13 +96,13 @@ While we're jumping a bit ahead, additionally, you can add an exclusion criteria
ansible-playbook site.yml --limit datacenter2 ansible-playbook site.yml --limit datacenter2
And if you want to read the list of hosts from a file, prefix the file name with '@'.:: And if you want to read the list of hosts from a file, prefix the file name with ``@``::
ansible-playbook site.yml --limit @retry_hosts.txt ansible-playbook site.yml --limit @retry_hosts.txt
Easy enough. See :ref:`intro_adhoc` and then :ref:`playbooks_intro` for how to apply this knowledge. Easy enough. See :ref:`intro_adhoc` and then :ref:`playbooks_intro` for how to apply this knowledge.
.. note:: You can use ',' instead of ':' as a host list separator. The ',' is preferred specially when dealing with ranges and ipv6. .. note:: You can use a comma (``,``) as a host list separator instead of a colon (``:``). The comma is preferred when dealing with ranges and IPv6 addresses.
.. seealso:: .. seealso::

Loading…
Cancel
Save