-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for full managed master.cf services #65
Allow for full managed master.cf services #65
Conversation
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.
Running the What do you think of changing this default to Also, I'd add a # This file managed by Salt, do not edit by hand!! or similar header |
@javierbertoli Sure, changing the default to false should be simple and probably makes sense. What about the changed defaults you mention? Are these changes happening on commented out services or on active ones? I'd be interested in seeing what changed as I based the services defaults on current upstream configuration examples... |
@ixs , they happen in both active and inactive ones, here's the output on a kitchen run:
It's quite possible the changes are Debian specific (that diverge from upstream). I bet the same happens in other platforms. That's why I always liked formulas to have this logic 😄 :
|
@ixs, @aboe76, I've been checking this formula and this PR, and found that the current state of the formula fails to configure master.cf: when you set policyd-spf:
enabled: true this section fails with
because the The error is still present in this PR because @ixs changes do not touch that section. Changing that piece of code to user=nobody argv={{ postfix.xbin_prefix }}/bin/policyd-spf will fix that error. With that, I'd say I'm OK with merging this PR as is. After all,
|
@javierbertoli will you create a PR for the |
@ixs and @javierbertoli thanks for testing and reviewing !! |
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.