Skip to content
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 user/playbook to specify dehyraded cron call #26

Open
eengstrom opened this issue Feb 26, 2021 · 0 comments · May be fixed by #27
Open

Allow user/playbook to specify dehyraded cron call #26

eengstrom opened this issue Feb 26, 2021 · 0 comments · May be fixed by #27

Comments

@eengstrom
Copy link
Contributor

eengstrom commented Feb 26, 2021

I had need to change the call made to dehydrated as embedded into the cron or systemd service. Also, there are subtle variations on the call to this scattered through the code. With the proposed change, one may change the command, adding arguments or even embed into a pipe to redirect output as needed.

Documentation and defaults added. Default value for new variable:

dehydrated_renew_command: "{{ dehydrated_install_root }}/dehydrated --cron"

Alternative example uses:

  • Don't give up on first failure:
dehydrated_renew_command: "{{ dehydrated_install_root }}/dehydrated --cron --keep-going"
  • More complicated example to redirect output to syslog:
dehydrated_renew_command: "bash -c '({{ dehydrated_install_root
}}/dehydrated -c -g | logger -t dehydrated -p local7.info) 2>&1 | logger
-t dehydrated -p local7.error -s'"

... although the latter is somewhat contrived and one would probably be
better served by using a systemd timer rather than a cron job, which
would then do effectively the same thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant