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
Currently master.cf only allows for _very_ limited configuration
options mainly focussed on SMTP submission settings.
This is rather limited and does not scale very well for managing
the other services defined in master.cf.
This patch has moved all the service definitions into a jinja file
and generates the master.cf service definition on the fly based on
these defaults.
Defaults can be overridden in a pillar to customize the rendered
master.cf file accordingly to local needs.
Undefined values will be filled with the postfix defaults.
Care has been taken that the previous ways of managing the submission
configuration options are still supported for backwards compatibility
to prevent breakage for existing users of the formula.