```
[213] SaltStack recommends using cmd.run together with onchanges, rather than cmd.wait
postfix/config.sls:148
cmd.wait:
[213] SaltStack recommends using cmd.run together with onchanges, rather than cmd.wait
postfix/init.sls:80
cmd.wait:
```
The new format match the format proposed in the template-formula
BREAKING CHANGE: as all resources' IDs changed, other formulas
depending on this formula's resources will need to be modified
accordingly.
Moved maps generation to config, and added dependency on main.cf generation. Solves centos8 problems.
Signed-off-by: Felipe Zipitria <fzipitria@perceptyx.com>
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.
The postfix service is currently being restarted whenever a
config item changes.
This is unnecessary as the postfix service can reload a new
config.
Set reload: True to prevent unnecessary restarts of the service.
The old behavior can be restored by setting the pillar key
reload_service to False.
According to postfix documentation [1], only some types of file require running
postmap, others must be left alone.
See github issue #50.
[1] http://www.postfix.org/postmap.1.html
Merge existing handling of postfix lookup table/map files into a single
template. Mappings are read from pillar in `postfix:mapping`.
Configuration is written to the file pointed to by the relevant
directive in `postfix:config`. A single target file is supported at the
moment. The file is postmap'ed if needed.
The pillar accepts a dict or an OrderedDict.
