Closed whereisaaron closed 2 years ago
MDChallengeDns01
has explicit setup and teardown calls so my use case above is not a good one. However I still think it would be better symmetry if MDMessageCmd had both setup and teardown messages.
Closing as I don't actually have a use case for this feature request, and MDMessageCmd challenge-setup
is called after a challenge has been set-up.
Feature request to add a
challenge-teardown:<type>:<domain>
toMDMessageCmd
.MDMessageCmd can be used to set up e.g. temporary DNS records for a DNS01 challenge when the
challenge-setup
message is received:However there is no corresponding message to tear down the challenge, e.g. delete the temporary DNS records for a DNS01 challenge, e.g.
The
renewed
orinstalled
MDMessageCmd messages could be used to do the tear-down, but the don't include the challenge type, so theMDMessageCmd
executable has to remember what challenges of what type it has set-up. If would enable more state-less message handling if there were an explicitchallenge-teardown
message.