Bug#838548: certbot: Please allow to easily set post-hooks

This has been fixed in Certbot's 0.19.0 release.

Bug#838548: certbot: Please allow to easily set post-hooks

On Sat, 25 Mar 2017 00:50:29 -0400 "Daniel Richard G." wrote: > Hooks are not passed to the "certbot renew" command, but are instead > saved in the /etc/letsencrypt/renewal/$DOMAIN.conf files. Indeed, this is the case. Below [renewalparams] you can specify: pre_hook =

Bug#838548: certbot: Please allow to easily set post-hooks

Hello bug, I think the original wishlist item is implemented as of 0.10.0. See this (closed) issue: https://github.com/certbot/certbot/issues/3394 Hooks are not passed to the "certbot renew" command, but are instead saved in the /etc/letsencrypt/renewal/$DOMAIN.conf files. Sylvain, could

Bug#838548: certbot: Please allow to easily set post-hooks

Package: certbot Version: 0.9.3-1~bpo8+1 Followup-For: Bug #838548 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, here's the patch consistent with Debian policies to accomplish that. Cheers, Ondrej - -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy:

Bug#838548: [Letsencrypt-devel] Bug#838548: certbot: Please allow to easily set post-hooks

tag 838548 +upstream thanks Sylvain writes: > It would be nice if the default crontab would allow to define post-hooks > without modifying the crontab, for example by running run-parts on a new > /etc/letsencrypt/post-hook.d/ directory. Hi Sylvain, Definitely

Bug#838548: certbot: Please allow to easily set post-hooks

Package: certbot Version: 0.8.1-2~bpo8+1 Severity: wishlist The current certbot package creates a /etc/cron.d/certbot file that takes care of renewing certificates. The only way to run post-hooks (eg. to restart the web server) at the moment is by modifying this file and adding the --post-hook