fix: detect zone dnssec as enabled when in pending status #1530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #1486
This PR does not fully fix that issue because it addresses two different errors and I think one of them is a bug either in the Cloudflare API or the Go client: #1486 (comment).
With this change, zones with DNSSEC in
pending
state (when the DS record has not been added or detected yet) won't throw aDNSSEC is already enabled
error. The code expected thestate
value of the DNSSEC API request was only one ofactive
ordisabled
, but thepending
state also represents an enabled DNSSEC, only that is not fully configured yet.