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

feature request: cron_after_command #285

Open
rbos opened this issue May 2, 2022 · 0 comments
Open

feature request: cron_after_command #285

rbos opened this issue May 2, 2022 · 0 comments

Comments

@rbos
Copy link

rbos commented May 2, 2022

Bit of a feature request. I think this could be just an oversight.

Background: all our domains were configured, for whatever reason, to use certbot in standalone mode. I'll probably change this. So they stop & start httpd.

How to reproduce (e.g Puppet code you use)

Create any letsencrypt rule using cron to run certbot with before/after hooks.

What are you seeing

When certbot fails for any reason in a cron run, there's no way to run a command if it fails, only if it succeeds.

So for instance, if you do:

cron_before_command  => '/bin/systemctl stop httpd',
cron_success_command => '/bin/systemctl start httpd',

then HTTPD will be stopped, certbot fails, and httpd will not be restarted, even if the failure was transient.

I'd like, perhaps, a "cron_after_command".

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

No branches or pull requests

1 participant