* Semi-automated using `ssf-formula` (v0.5.0)
* Fix (or ignore) errors shown below:
```bash
postfix-formula$ $(grep "\- yamllint" .travis.yml | sed -e "s:^\s\+-\s\(.*\):\1:")
./postfix/osfamilymap.yaml
1:1 warning missing document start "---" (document-start)
./postfix/services.yaml
11:1 warning missing document start "---" (document-start)
12:1 warning comment not indented like content (comments-indentation)
221:1 warning comment not indented like content (comments-indentation)
./postfix/defaults.yaml
4:1 warning missing document start "---" (document-start)
pillar.example
1:1 warning missing document start "---" (document-start)
2:25 warning truthy value should be one of [false, true] (truthy)
13:17 warning truthy value should be one of [false, true] (truthy)
16:17 warning truthy value should be one of [false, true] (truthy)
22:17 warning truthy value should be one of [false, true] (truthy)
23:17 warning truthy value should be one of [false, true] (truthy)
25:17 warning truthy value should be one of [false, true] (truthy)
29:17 warning truthy value should be one of [false, true] (truthy)
31:17 warning truthy value should be one of [false, true] (truthy)
35:17 warning truthy value should be one of [false, true] (truthy)
47:15 warning truthy value should be one of [false, true] (truthy)
50:18 warning truthy value should be one of [false, true] (truthy)
53:21 warning truthy value should be one of [false, true] (truthy)
62:24 warning truthy value should be one of [false, true] (truthy)
66:31 warning truthy value should be one of [false, true] (truthy)
69:19 warning truthy value should be one of [false, true] (truthy)
70:19 warning truthy value should be one of [false, true] (truthy)
73:14 warning truthy value should be one of [false, true] (truthy)
74:21 warning truthy value should be one of [false, true] (truthy)
78:14 warning truthy value should be one of [false, true] (truthy)
89:15 error trailing spaces (trailing-spaces)
96:6 warning missing starting space in comment (comments)
130:89 error line too long (105 > 88 characters) (line-length)
131:89 error line too long (101 > 88 characters) (line-length)
152:5 error duplication of key "sender_canonical_maps" in mapping (key-duplicates)
154:5 error duplication of key "virtual_alias_maps" in mapping (key-duplicates)
190:5 error duplication of key "use_file" in mapping (key-duplicates)
235:9 error wrong indentation: expected 10 but found 8 (indentation)
248:1 error duplication of key "postfix" in mapping (key-duplicates)
258:85 error trailing spaces (trailing-spaces)
```
The services definitions for master.cf were previously defined in
the services.jinja file.
This commit instead moves them into the services.yaml file, as we
should not require any jinja parsing inside the services definitions.
Drive-By: Add a .gitignore file
Drive-By: Set manage_master_config: True for kitchen. We do want to
verify that the master.cf file generation is actually working.
Drive-By: Add fedora-latest as a kitchen testing target, this helps
with verifying the os_family map testing that was added in
PR #79
Drive-By: Link to the kitchen-salt getting started guide in the README
Add dovecot example using the services dictionary with a note that
LMTP delivery might be better.
Slight improvements about pillar example settings.
Reorder examples, put the services dictionary examples which allow
more control above the previous dovecot and submission examples.
Add a note about backwards compatibility to indicate that these
options are still supported.
http://www.postfix.org/DATABASE_README.html#types specifies the lookup
table types postfix understands.
Most are defined as type:/path/to/table which is currently supported
by the postfix formula.
This does break though as soon as the proxy table type is used which is
a prefix to a normal table definition to indicate caching is requested.
This PR changes the code to discard the proxy prefix to ensure that the
usual logic applies again.
Issue #68 raised a valid problem: The postfix formula is using
the osmap.yaml file incorrectly. It is being used to filter on
the os grain but should instead be filtering on os_family
to correctly account for Red Hat/CentOS similarities.
PR #69 did the fix in a complex way as it only moved parts of the os
mapping into the os_family mapping.
This is a much simpler fix, as it just renames the file and uses
it as a os_family map, which it actually is.
If we really need to differentiate between os flavors inside the
os_family at a later date, we can then add a lookup on the os grain.
No need to complicate manners now.
