Closed fzipi closed 4 years ago
Best reviewed: commit by commit
Powered by Pull Assistant. Last update d87da4a ... d87da4a. Read the comment docs.
I don't think testing with centos6 and salt 2017 would make any good nowadays...
I don't think testing with centos6 and salt 2017 would make any good nowadays...
@fzipi Yes, don't worry about that, we're in the process of removing these but we're waiting for the latest release (tomorrow) before upgrading Travis (again).
In the meantime, we need one of the Postfix contributors to have a look at this PR. Let's see if @alxwr or @ixs wouldn't mind having a look.
Hi @alxwr @ixs, can you review this PR?
@daks Since there's no response from the others, any chance of a general review here?
@fzipi If there's no activity in a couple of days, please ping me directly and I'll try to write some tests for this, so at least we're confirming the implementation that way. Or if you'd like to have a go, please make sure to add any pillar values to test/salt/pillar/default.sls
so that your states run in Kitchen. These are the only states of config.sls
that are running at the moment:
Appreciate you making time to review this, @daks.
@fzipi So all this needs before it can be merged is to add tls_policy
to the pillar.example
, as @daks has mentioned above.
@myii Done!
@daks I get what you are saying. I have some inspec tests, maybe would push them in a new PR if interested.
Also, now that I see this again. maybe all maps should be below mapping
key, and treat them equally. Will try that and if is seems reasonable maybe create a new PR.
Thanks!
Felipe.
Merged, thanks to you both @fzipi and @daks.
:tada: This PR is included in version 0.19.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Signed-off-by: Felipe Zipitria fzipitria@perceptyx.com
This PR adds
smtp_tls_policy_maps
. See postfix TLS readmePR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context