Expand description
Error type and the wire-shape Firecracker uses for failed requests.
Status code mapping (per 20-firecracker-api.md § 3):
- 400 Bad Request — malformed JSON, missing required fields, invalid enum values, illegal state transitions, unknown paths (Firecracker collapses 404 to 400 for the wire compat-suite shape), validation failures.
- 413 Payload Too Large — bodies above
--http-api-max-payload-size, oversized MMDS data store mutations. - 500 Internal Server Error — VMM event loop is gone; rare and logged at
error. - 504 Gateway Timeout — squib-only; emitted when a per-action-class timeout (70-security.md
§ 6) fires while the controller awaits the
VMM. Upstream Firecracker has no 504; orchestrators should retry with the same idempotency
key. Documented in
docs/api-deviations.md.
Successful PUT/PATCH/DELETE produce 204 No Content directly without an ApiError.
Structs§
- Fault
Message - The exact JSON body upstream Firecracker emits on every failed API call.
Enums§
- ApiError
- Errors produced by API handlers, each carrying the HTTP status code Firecracker returns for that class of failure.
Type Aliases§
- Result
- Result alias used throughout
squib-api.