devnomads 0.5.0__tar.gz → 0.6.1__tar.gz

devnomads-0.5.0/README.md → devnomads-0.6.1/PKG-INFO

@@ -1,3 +1,21 @@
+Metadata-Version: 2.5
+Name: devnomads
+Version: 0.6.1
+Summary: Python client library for the DevNomads API (transport, DNS, ACME)
+Project-URL: Homepage, https://devnomads.nl
+Author-email: DevNomads <support@devnomads.nl>
+License: MIT
+Keywords: acme,api,devnomads,dns,powerdns
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Provides-Extra: acme
+Requires-Dist: acme>=2.11; extra == 'acme'
+Requires-Dist: cryptography>=42; extra == 'acme'
+Requires-Dist: dnspython>=2.6; extra == 'acme'
+Requires-Dist: josepy>=1.14; extra == 'acme'
+Requires-Dist: requests>=2.31; extra == 'acme'
+Description-Content-Type: text/markdown
+
 # devnomads
 
 Python client library for the [DevNomads](https://devnomads.nl) API:
@@ -172,6 +190,11 @@ JSON and:
   resource reads as absence;
 - raises `AuthError` on `401`/`403` and `ApiError` on any other `4xx`.
 
+`send(method, path, *, params=None, json_body=None, timeout=None)` does
+the same but returns a `Response` with `status`, `headers` and `data`,
+and treats every non-2xx status as an error, a `404` included.
+`timeout` overrides the client's request timeout for that call.
+
 ## Services
 
 Beyond the curated DNS and ACME helpers, the `Client` exposes the rest
@@ -194,9 +217,18 @@ with Client.from_environment() as client:
 
 The top-level resources are `servers`, `databases`, `emails`, `spams`,
 `containers`, `proxies`, `sites`, `buckets`, `domains`, `forwards`,
-`searches`, `apps`, and `handles`. (DNS stays the curated
+`searches`, `apps`, `handles`, `keys`, `jobs`, `clients`, `invoices`,
+`products`, and `services` (operations on any service, such as
+`client.services.jobs.list(service_id)`). (DNS stays the curated
 `devnomads.dns` interface and is not generated here.)
 
+Many create, update and delete calls run in the background: they
+answer `202` with the list of queued jobs, all in one batch. Follow it
+with `client.jobs.batches.show(batch_id)` until every job's `status`
+is `completed`, `failed` or `cancelled`. Use `client.send(...)` instead
+of `request` when you also need the status code or the `Location`
+header that points at the batch.
+
 ### Conventions
 
 - **Path parameters** are positional, in URL order, snake-cased from

devnomads-0.5.0/PKG-INFO → devnomads-0.6.1/README.md

@@ -1,21 +1,3 @@
-Metadata-Version: 2.4
-Name: devnomads
-Version: 0.5.0
-Summary: Python client library for the DevNomads API (transport, DNS, ACME)
-Project-URL: Homepage, https://devnomads.nl
-Author-email: DevNomads <support@devnomads.nl>
-License: MIT
-Keywords: acme,api,devnomads,dns,powerdns
-Requires-Python: >=3.10
-Requires-Dist: httpx>=0.27
-Provides-Extra: acme
-Requires-Dist: acme>=2.11; extra == 'acme'
-Requires-Dist: cryptography>=42; extra == 'acme'
-Requires-Dist: dnspython>=2.6; extra == 'acme'
-Requires-Dist: josepy>=1.14; extra == 'acme'
-Requires-Dist: requests>=2.31; extra == 'acme'
-Description-Content-Type: text/markdown
-
 # devnomads
 
 Python client library for the [DevNomads](https://devnomads.nl) API:
@@ -190,6 +172,11 @@ JSON and:
   resource reads as absence;
 - raises `AuthError` on `401`/`403` and `ApiError` on any other `4xx`.
 
+`send(method, path, *, params=None, json_body=None, timeout=None)` does
+the same but returns a `Response` with `status`, `headers` and `data`,
+and treats every non-2xx status as an error, a `404` included.
+`timeout` overrides the client's request timeout for that call.
+
 ## Services
 
 Beyond the curated DNS and ACME helpers, the `Client` exposes the rest
@@ -212,9 +199,18 @@ with Client.from_environment() as client:
 
 The top-level resources are `servers`, `databases`, `emails`, `spams`,
 `containers`, `proxies`, `sites`, `buckets`, `domains`, `forwards`,
-`searches`, `apps`, and `handles`. (DNS stays the curated
+`searches`, `apps`, `handles`, `keys`, `jobs`, `clients`, `invoices`,
+`products`, and `services` (operations on any service, such as
+`client.services.jobs.list(service_id)`). (DNS stays the curated
 `devnomads.dns` interface and is not generated here.)
 
+Many create, update and delete calls run in the background: they
+answer `202` with the list of queued jobs, all in one batch. Follow it
+with `client.jobs.batches.show(batch_id)` until every job's `status`
+is `completed`, `failed` or `cancelled`. Use `client.send(...)` instead
+of `request` when you also need the status code or the `Location`
+header that points at the batch.
+
 ### Conventions
 
 - **Path parameters** are positional, in URL order, snake-cased from