Skip to content

feature request: cron_after_command #285

@rbos

Description

@rbos

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".

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions