Different hooks for different operations #208

New Issue

2025-12-29T01:18:58+01:00

adam commented

2025-12-29 01:18:58 +01:00

Originally created by @pv2b on GitHub (Mar 30, 2017).

Currently the HOOK variable is used like this (from the default config file)

Program or function called in certain situations

After generating the challenge-response, or after failed challenge (in this case altname is empty)
Given arguments: clean_challenge|deploy_challenge altname token-filename token-content

After successfully signing certificate
Given arguments: deploy_cert domain path/to/privkey.pem path/to/cert.pem path/to/fullchain.pem

BASEDIR and WELLKNOWN variables are exported and can be used in an external program
default: <unset>

IMO this does not make much sense because, in the case of DNS-01 challenges, challenge deployment is completely unrelated to certificate deployment.

A useful feature would therefore be to be able to specify different hooks for different operations, for example HOOK_DEPLOY_CERT would be called for deploy_cert operations. If HOOK_DEPLOY_CERT were unset, HOOK would be called instead, thereby preserving backwards compatibility. Of course the other operations would get their own environment variables as well.

This is more of a "nice to have" though, because it's pretty trivial to work around this limitation by making a hook that simply "routes" the right hook calls to the right script.

Originally created by @pv2b on GitHub (Mar 30, 2017). Currently the HOOK variable is used like this (from the default config file) > Program or function called in certain situations > > After generating the challenge-response, or after failed challenge (in this case altname is empty) > Given arguments: clean_challenge|deploy_challenge altname token-filename token-content > > After successfully signing certificate > Given arguments: deploy_cert domain path/to/privkey.pem path/to/cert.pem path/to/fullchain.pem > > BASEDIR and WELLKNOWN variables are exported and can be used in an external program > default: \<unset\> IMO this does not make much sense because, in the case of DNS-01 challenges, challenge deployment is completely unrelated to certificate deployment. A useful feature would therefore be to be able to specify different hooks for different operations, for example HOOK_DEPLOY_CERT would be called for deploy_cert operations. If HOOK_DEPLOY_CERT were unset, HOOK would be called instead, thereby preserving backwards compatibility. Of course the other operations would get their own environment variables as well. This is more of a "nice to have" though, because it's pretty trivial to work around this limitation by making a hook that simply "routes" the right hook calls to the right script.

adam closed this issue

2025-12-29 01:18:58 +01:00

adam commented

2025-12-29 01:18:59 +01:00

@lukas2511 commented on GitHub (Jul 10, 2017):

Just use a master-script that distributes the hooks to other scripts, no need to implement this in dehydrated.

@lukas2511 commented on GitHub (Jul 10, 2017): Just use a master-script that distributes the hooks to other scripts, no need to implement this in dehydrated.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#208