Compound matchers allow very granular minion targeting using any of the previously discussed matchers. The default matcher is a glob, as usual. For matching via anything other than glob, preface it with the letter denoting the match type. The currently implemented "letters" are:
| Letter | Meaning | Example |
|---|---|---|
| G | Grains glob match | G@os:Ubuntu |
| E | PCRE Minion id match | E@web\d+\.(dev|qa|prod)\.loc |
| P | Grains PCRE match | P@os:(RedHat|Fedora|CentOS) |
| L | List of minions | L@minion1.example.com,minion3.domain.com or bl*.domain.com |
| I | Pillar glob match | I@pdata:foobar |
| S | Subnet/IP addr match | S@192.168.1.0/24 or S@192.168.1.100 |
| R | Range cluster match | R@%foo.bar |
| D | Minion Data match | D@key:value |
Matchers can be joined using boolean and, or, and not operators.
For example, the following command matches all minions that have a hostname that begins with "webserv" and that are running Debian or it matches any minions that have a hostname that matches the regular expression web-dc1-srv.*:
salt -C 'webserv* and G@os:Debian or E@web-dc1-srv.*' test.ping
That same example expressed in a top file looks like the following:
base:
'webserv* and G@os:Debian or E@web-dc1-srv.*':
- match: compound
- webserver
Note that you cannot have a leading not in a command. Instead you must do something like the following:
salt -C '* and not G@kernel:Darwin' test.ping