Follow-up to the sweep route audit, correcting its diagnosis: the CLI
DOES read .yml bodies — via OpenCollection's `body.data` string form
(the NewDevDBSetup script always worked because it used it). The
failing scenario POSTs used `body.json` (structured) / `body.jsonBody`
(string) — keys the CLI silently ignores, sending Content-Length: 0
with form-urlencoded content-type, so every server bind failed.
- 81 bodies converted to data-form (json maps serialized; jsonBody
strings kept verbatim, {{vars}} intact).
- 6 pre-existing TRUNCATED payloads repaired: the original generator
cut bodies at the first {{var}} (every SHA-256-identified scenario
plus Sync Progress/Sync Bookmarks shipped mid-JSON and 400'd from
day one). Rewritten whole, faithful to each file's documented
purpose; book_sha256/book_uuid added to the environment.
- environments: opds_base_url correction from the sweep retained.
Verified live against the rebuilt dev container: the full koreader
scenario tree runs green through `bru run` — 14/14 (202s across
immediate/checkpoint/SHA-256 progress, 200s bookmarks, highlights,
notes; SHA-256 book identification exercised against a real
file_sha256).
85 lines
1.6 KiB
YAML
85 lines
1.6 KiB
YAML
info:
|
|
name: Update Device Settings
|
|
type: http
|
|
seq: 7
|
|
http:
|
|
method: PUT
|
|
url: '{{base_url}}/api/devices/{{device_id}}'
|
|
auth: inherit
|
|
headers:
|
|
- key: Content-Type
|
|
value: application/json
|
|
body:
|
|
type: json
|
|
data: "{\n \"device_name\": \"Updated Device Name\",\n \"sync_enabled\": true,\n \"auto_sync\": true,\n \"sync_frequency_minutes\": 10\n}"
|
|
docs: '## Update Device Settings
|
|
|
|
|
|
Updates device configuration and sync settings.
|
|
|
|
|
|
**Method:** PUT
|
|
|
|
|
|
**Endpoint:** /api/devices/:device_id
|
|
|
|
|
|
**Authentication:** Required (Bearer token)
|
|
|
|
|
|
**Path Parameters:**
|
|
|
|
- `device_id` (string): UUID of the device
|
|
|
|
|
|
**Request Body:**
|
|
|
|
- `device_name` (string, optional): New device name
|
|
|
|
- `sync_enabled` (boolean, optional): Enable/disable sync
|
|
|
|
- `auto_sync` (boolean, optional): Enable automatic sync
|
|
|
|
- `sync_frequency_minutes` (integer, optional): Sync interval (5-1440 minutes)
|
|
|
|
|
|
**Response:**
|
|
|
|
- `id` (string): Device UUID
|
|
|
|
- `device_name` (string): Updated device name
|
|
|
|
- `sync_enabled` (boolean): Updated sync status
|
|
|
|
- `auto_sync` (boolean): Updated auto-sync setting
|
|
|
|
- `sync_frequency_minutes` (integer): Updated sync interval
|
|
|
|
- `updated_at` (string): Update timestamp
|
|
|
|
|
|
**Status Codes:**
|
|
|
|
- 200: Settings updated successfully
|
|
|
|
- 400: Invalid sync frequency or data
|
|
|
|
- 401: Unauthorized
|
|
|
|
- 403: Forbidden (device belongs to different user)
|
|
|
|
- 404: Device not found
|
|
|
|
|
|
**Sync Frequency Guidelines:**
|
|
|
|
- Mobile devices: 10-30 minutes
|
|
|
|
- E-readers on WiFi: 15-60 minutes
|
|
|
|
- Web clients: 5-15 minutes
|
|
|
|
- Minimum: 5 minutes
|
|
|
|
- Maximum: 1440 minutes (24 hours)'
|