v2.8.0: Fix regression with set challenges being ignored #40
Manually merged
coolaj86
於 5 年之前 將 1 次代碼提交從 dns-challenge-regression-fix
合併至 master
Loading…
Reference in new issue
尚未有任何內容
Delete Branch 'dns-challenge-regression-fix'
Deleting a branch is permanent. It CANNOT be undone. Continue?
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 ignoredto v2.8.0: Fix regression with set challenges being ignored 5 年之前c8b895633c
.