ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-07-08 22:30:04 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Rename 'yamlscripts' to 'yamlsyntax', add some extra crosslinking to make sure folks find the

Browse source 
interesting docs pages, some misc editing here and there.
This commit is contained in:
Michael DeHaan 2012-03-11 15:34:21 -04:00
parent 02549869b1
commit d3fe5f617a
22 changed files with 219 additions and 165 deletions
Download patch file Download diff file Expand all files Collapse all files

17
rst/patterns.rst
View file

@ -34,6 +34,8 @@ looks like this::
two.example.com
three.example.com
The things in brackets are group names, you don't have to have them,
but they are useful.
Selecting Targets
+++++++++++++++++
@ -43,19 +45,20 @@ These patterns target all hosts in the inventory file::
all
*
It is also possible to address specific hosts::
Basically 'all' is an alias for '*'. It is also possible to address a specific host or hosts::
one.example.com
one.example.com:two.example.com
192.168.1.50
192.168.1.*
The following patterns address one or more groups, which are denoted
with the bracket headers in the inventory file::
with the aforementioned bracket headers in the inventory file::
webservers
webservers:dbservers
Individual hosts, but not groups, can also be referenced using
Individual host names (or IPs), but not groups, can also be referenced using
wildcards::
*.example.com
@ -66,4 +69,8 @@ It's also ok to mix wildcard patterns and groups at the same time::
one*.com:dbservers
.. note::
It is not possible to target a host not in the inventory file.
It is not possible to target a host not in the inventory file. This is a safety feature.
Easy enough. Now see :doc:`examples` and then :doc:`playbooks` for how to do things to selected hosts.