fix: stable and consistent paging of DNS records (#2)

- list DNS records with order=name&direction=asc, without an order
  Cloudflare's pages can overlap and miss records
- de-duplicate fetched entries by ID, fetch the pages again (up to 3
  times) if fewer entries than total_count were fetched, otherwise log
  a warning; debug log per fetched page
- testPaging: unique record names for an unambiguous order
- testDns: wait for the unfiltered record list, which can lag behind
  directly after creating records

refs #2

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
thischwaandClaude Opus 5.5 committed 2026-11-04 14:43:22 +01:00
1 parent 6eb6c2b778
commit 09eabb0d59
4 files changed
+160 -28

No files matched your search

+1
View File
@@ -33,6 +33,7 @@
- fixed: `zoneGet` threw an `IndexOutOfBoundsException` for unknown zones, it now returns `null` or throws a `CloudflareNotFoundException` (depending on `emptyResultThrowsException`)
- fixed: `getSubdomain()` failed for apex records and records with multi-level subdomains, batch operations now send the full record name
- fixed: `zoneList()` and `recordList(...)` without `PagingRequest` returned only the first page, now all pages are fetched
- fixed: DNS records are listed with a stable order (`order=name`), because without it Cloudflare's pages can overlap and miss records; fetched records are de-duplicated and inconsistent pages are fetched again
- fixed: `recordDelete` threw a `NullPointerException` for an empty result
- 0.5.0:
- moved the project to git.mein-gateway.de