Originally created by @basbebe on GitHub (Feb 25, 2020).
The deploy_challenge hook is being called once for every domain and alternative name.
I'm waiting 900s for each DNS record to propagate (safest with my provider).
At this point, this makes e.g. 900s x 4 if I have a certificate with three alternative names.
Is there a possibility for me to only wait once after all the records are created before the challenge?
Otherwise it would be nice to have an additional pre-challenge hook or the like…
Originally created by @basbebe on GitHub (Feb 25, 2020).
The deploy_challenge hook is being called once for every domain and alternative name.
I'm waiting 900s for each DNS record to propagate (safest with my provider).
At this point, this makes e.g. 900s x 4 if I have a certificate with three alternative names.
Is there a possibility for me to only wait once after all the records are created before the challenge?
Otherwise it would be nice to have an additional pre-challenge hook or the like…
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 @basbebe on GitHub (Feb 25, 2020).
The deploy_challenge hook is being called once for every domain and alternative name.
I'm waiting 900s for each DNS record to propagate (safest with my provider).
At this point, this makes e.g. 900s x 4 if I have a certificate with three alternative names.
Is there a possibility for me to only wait once after all the records are created before the challenge?
Otherwise it would be nice to have an additional pre-challenge hook or the like…
@txr13 commented on GitHub (Feb 25, 2020):
You want to use HOOK_CHAIN: https://github.com/dehydrated-io/dehydrated/blob/master/docs/hook_chain.md
@basbebe commented on GitHub (Feb 25, 2020):
yes I do!
thank you @txr13
I don't know yet how to parse all the arguments though
@basbebe commented on GitHub (Feb 25, 2020):
got it:
@basbebe commented on GitHub (Feb 25, 2020):
got it: