-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: Added postfix_files feature as a simple means to add extra files/maps to config #129
feat: Added postfix_files feature as a simple means to add extra files/maps to config #129
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, please add an entry to README.md about postfix_files
and a test.
handlers/main.yml
Outdated
loop: "{{ postfix_files }}" | ||
loop_control: | ||
loop_var: file | ||
changed_when: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This task results in a change, is it? Is there a way to make it idempotent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sadly, no, there's no output for postmap and the exit code is always 0 (when it succeeds)
root@debian:~# touch file
root@debian:~# postmap file # creating a new file.db file
root@debian:~# echo $?
0
root@debian:~# postmap file # updates the existing file.db file
root@debian:~# echo $?
0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can it list created files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should not do this in a handler - see below
please rebase on the latest |
[citest] |
1 similar comment
[citest] |
Rebase done! :) |
[citest] |
@Thulium-Drake https://github.com/Thulium-Drake/ansible-role-postfix/pull/1 to fix test failures and rebase to latest |
53b0c22
to
54b326a
Compare
This should do it then :-) |
Unfortunately, the PR cannot be merged - I tried to fix this locally and push to your branch to update the PR:
I think you have to explicitly give permission for role maintainers to do this - see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork If you don't want to do this, then you'll need to rebase and squash - try this:
|
46d8dcd
to
d96af19
Compare
… to the postfix config
d96af19
to
c7ba240
Compare
I tried the access route, but it didn't pan out. Thanks for the instructions on how to rebase (I don't do that too often 😅 )! Should be good now (?) 🚀 |
[citest] |
Enhancement: Added a means to configure extra files for Postfix
Reason: Some config options require to pick up additional information from a file (e.g. with SASL credentials etc). This PR adds 'postfix_files', a simple means of creating these files and integrating them in the Postfix configuration.
Result:
Issue Tracker Tickets (Jira or BZ if any):