v2.8.0: Fix regression with set challenges being ignored #40
Fusionado manualmente
coolaj86
fusionados 1 commits de dns-challenge-regression-fix
en master
hace 5 años
Cargando…
Referencia en una nueva incidencia
Aún no existe contenido.
Eliminar la rama con el nombre 'dns-challenge-regression-fix'
Eliminar una rama es permanente. NO PUEDE deshacerse. ¿Continuar?
Regression Fix
Backwards compatibility madness.
When you Greenlock.create({ }), challenges will be set by default if
not available. This is good... ish.
When you approveDomains() and set opts.challenges, however, those must
be able to override the defaults.
This was just recently broken and the fix seems to be to make the prior
defaults inaccessible, otherwise it becomes really confusing as to why
a set DNS challenge for local, wild, or private domains is not being
preferred to the (failing) http.
All this crap will be cleaned up in v3...
New Feature
Oh, and this adds support for
getZones()
, the testing of which brought about the need to fix the regression.Fix regression with set challenges being ignoreda v2.8.0: Fix regression with set challenges being ignored hace 5 añosc8b895633c
.