add hook for propagate_challenge #481

Closed
opened 2025-12-29 01:26:00 +01:00 by adam · 2 comments
Owner

Originally created by @jeffgoh on GitHub (Jun 29, 2020).

Whilst I can add a wait for each challenge to propagate, if I have say 10 challenges, that's 10 DNS propagations to wait for, which is inefficient. Much more efficient to add one more hook for propagate_challenge. Will file a pull request shortly.

Originally created by @jeffgoh on GitHub (Jun 29, 2020). Whilst I can add a wait for each challenge to propagate, if I have say 10 challenges, that's 10 DNS propagations to wait for, which is inefficient. Much more efficient to add one more hook for propagate_challenge. Will file a pull request shortly.
adam closed this issue 2025-12-29 01:26:00 +01:00
Author
Owner

@c-MM commented on GitHub (Jun 29, 2020):

I use HOOK_CHAIN="yes" to get all challenges at once and deploy them. Maybe this is what you need?

@c-MM commented on GitHub (Jun 29, 2020): I use HOOK_CHAIN="yes" to get all challenges at once and deploy them. Maybe this is what you need?
Author
Owner

@lukas2511 commented on GitHub (Jul 4, 2020):

Use HOOK_CHAIN and configure your hook script to wait for challenge propagation. Any other way is either already solvable in hook scripts, or would break order of operations which is important for a lot of setups.

@lukas2511 commented on GitHub (Jul 4, 2020): Use HOOK_CHAIN and configure your hook script to wait for challenge propagation. Any other way is either already solvable in hook scripts, or would break order of operations which is important for a lot of setups.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#481