v2.8.0: Fix regression with set challenges being ignored #40
Manually merged
coolaj86
aplicou merge dos 1 commits de dns-challenge-regression-fix
em master
5 anos atrás
Carregando…
Reference in new issue
Ainda não há conteúdo.
Excluir branch 'dns-challenge-regression-fix'
A exclusão de uma branch é permanente. Isto NÃO PODERÁ ser desfeito. 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 ignoredpara v2.8.0: Fix regression with set challenges being ignored 5 anos atrásc8b895633c
.