Closed norman-zon closed 10 months ago
CC @costasd (maintainer of the NS1 provider)
Thanks, will take a look!
So, looks like this ending up a warning is not ns1-specific (an error is actually emitted for such). The warning looks like it's a warning on purpose when ensuring a zone, so that it doesn't fail the run completely in case of multiple providers.
Looking at the code below the snippet, I see that it actually avoids attempting any further operations to the broken provider (such as records or registrar updates to add nameservers) - so it's safe.
Given that it's safe as it is, I don't see a lot of improvements to be made, besides maybe error on our way out during reporting something like Ensuring zone X in provider Y failed with message
?
Would that improve it?
Would it be an option to use some other exit code than 0 or 1 for a "partial" success. Or run the others providers, but still exit with 1
?
In my case I would like to send a notification/alert from a CI run, in the above case.
I see. Makes sense needing to know about this. I've thought of an approach relative to what you suggest, I'll give it a try.
Describe the bug When getting a
524 Origin Time-out
response from NS1, the provider handles it as a WARNING anddnscontrol
exits successfully.To Reproduce I can't figure out how to reproduce a 524.
Here is a log of one occurence:
Expected behavior A 524 Error should be handled as an error and lead to
dnscontrol
failing with a non-zero exit codeDNS Provider NS1
Additional context dnscontrol v4.4.1