Align pagination with Cloudflare API limits Co-authored-by: Junie <junie@jetbrains.com>
This commit is contained in:
1 parent
7aab2e9610
commit
369c584f5f
11 files changed
+185
-62
No files matched your search
+5
-6
@@ -6,6 +6,8 @@
|
||||
- `recordList(zone, String subdomain, RecordType... types)` and `recordList(zone, String subdomain)` → `recordListBySubdomain(zone, subdomain, types...)`
|
||||
- `recordList(zone, RecordType... types)` → `recordListByType(zone, types...)`
|
||||
- `recordList(zone)` and `recordList(zone, PagingRequest)` remain unchanged
|
||||
- `CfDnsClient#recordCreateSld(...)` was removed; use `recordCreateSubdomain(...)`
|
||||
- `PagingRequest.defaultPaging()` now requests 50 items instead of 1,000. Page numbers and page sizes are validated; zone requests accept 5–50 items per page, while DNS record requests accept 1–5,000,000.
|
||||
- `withBaseUrl` only accepts HTTPS URLs (plain HTTP only for loopback hosts like `localhost`), otherwise an `IllegalArgumentException` is thrown
|
||||
- `build()` throws an `IllegalStateException` if no authentication was configured, `null` credentials throw an `IllegalArgumentException`
|
||||
- zone names and subdomains with whitespace, control characters or `\ ? # & ; | < > " ' `` ` `` are rejected with an `IllegalArgumentException`, zone and record IDs must be alphanumeric
|
||||
@@ -23,16 +25,13 @@
|
||||
- filtering by exactly one record type is done by Cloudflare (`?type=`), unknown record types in responses don't break the client-side filter anymore
|
||||
- updated dependencies: jackson 3.2.4, httpclient5 5.6.4, lombok 1.18.48, logback-classic 1.6.6, mockito-junit-jupiter 5.24.0
|
||||
- updated maven plugins: maven-compiler-plugin 3.16.0, maven-surefire-plugin 3.6.0, maven-jar-plugin 3.5.1
|
||||
- README: fixed fluent API examples, documented paging and further methods
|
||||
- fixed "getRecord" wording in javadoc, log and exception messages (e.g. "Invalid record type")
|
||||
- **Deprecation**: the misleading term "sld" was renamed to "subdomain", the old methods will be removed in a future release:
|
||||
- `RecordEntity#getSld()` → `RecordEntity#getSubdomain()`
|
||||
- `CfDnsClient#recordCreateSld(...)` → `CfDnsClient#recordCreateSubdomain(...)`
|
||||
- fixed "getRecord" wording in log and exception messages (e.g. "Invalid record type")
|
||||
- **Deprecation**: the misleading term "sld" was renamed to "subdomain": `RecordEntity#getSld()` is deprecated for removal; use `RecordEntity#getSubdomain()`
|
||||
- `getSubdomain()` returns `"@"` for the zone apex; `CfDnsClient.APEX` can be used to address the zone apex
|
||||
- fixed: API errors were wrapped into a generic "Unexpected error!" exception
|
||||
- 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: `zoneList()` and `recordList(...)` without `PagingRequest` returned only the first page, now all pages are fetched; `recordList(zone, null)` uses the maximum DNS page size of 5,000,000
|
||||
- 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:
|
||||
|
||||
Reference in new issue
Block a user