Supported operations
Request sequence
Guarantees and non-guarantees
A successful dry run confirms that the request passed validation at that moment. It does not:- reserve an identifier, resource, name, or position
- lock the resource
- create an idempotency record
- guarantee the subsequent write will succeed
- create a separate test environment
- suppress reads of current production data
409 and 422 again on the real request.
Preview identifiers
A create dry run can return a preview ID. Do not store it as the real resource ID and do not reference it in later requests. Persist only the identifier returned by the successful non-dry-run create response.Safe usage pattern
1
Build the final request
Use the same headers and body intended for the real write.
2
Validate with dryRun=true
Inspect both the projected resource and any validation error.
3
Apply without delay
Send the final write after the projection is accepted.
4
Reconcile the response
Store the real resource ID, state, and
X-Request-ID.