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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
@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?
@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.