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.

Sign up for GitHub

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

Jump to bottom

Need consistent approach in using pre/post/deploy hooks with certonly and renew subcommands #9869

Open

rakesh-p opened this issue Jan 4, 2024 · 0 comments

rakesh-p commented Jan 4, 2024

I have been asked to post my question here https://community.letsencrypt.org/t/reasoning-behind-hooks-directory-available-only-for-certficate-renewal/211182/

The usage is not similar when it comes to hooks for certonly and renew subcommands.

Just like 'renew' subcommand, it is possible to specify hooks via flags like --pre-hook, --post-hook for certonly but it is not documented (e.g. in 'certbot -h certonly'. )
It is possible to use the directories/folders (pre/post/deploy) with scripts with the renew subcommand but not with the certonly subcommand

It would be nice to:

update the documentation for certonly to show flags --pre-hook etc.
support folders (pre/post/deploy) for certonly as well

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment