v2.8.0: Fix regression with set challenges being ignored #40

手動マージ済み
coolaj86 が 1 個のコミットを dns-challenge-regression-fix から master へマージ 2019-06-14 09:28:29 +00:00
オーナー

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.

# 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.
coolaj86 がプルリクエストをクローズ 2019-06-14 09:28:29 +00:00
coolaj86 がタイトルを Fix regression with set challenges being ignored から v2.8.0: Fix regression with set challenges being ignored に変更 2019-06-14 09:28:58 +00:00
サインインしてこの会話に参加。
レビューアなし
ラベルなし
1 人の参加者
通知
期日
期日は未設定です。
依存関係

依存関係が設定されていません。

リファレンス: coolaj86/greenlock.js-ARCHIVED#40
説明はありません。