Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: do not pass netcup API error in some case #42

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

aellwein
Copy link
Owner

Netcup API responds with an error response (status "error", code 5209), see discussion in mrueg/external-dns-netcup-webhook#5. In order to make this error recoverable, we add a special treatment for exactly this kind of error upon calling of InfoDnsRecords().

Fixes: #41
Refs: mrueg/external-dns-netcup-webhook#5

Netcup API responds with an error response (status "error", code 5209),
see discussion in mrueg/external-dns-netcup-webhook#5. In order to
make this error recoverable, we add a special treatment for exactly
this kind of error upon calling of InfoDnsRecords().

Fixes: #41
Refs: mrueg/external-dns-netcup-webhook#5
@aellwein aellwein merged commit a4ffdb5 into main Jan 30, 2024
@aellwein aellwein deleted the fix/empty_dns_records branch January 30, 2024 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle the empty DNS zone case (netcup API returns an error)
1 participant