John O'Keefe
09b6693505
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).
64 lines
1.3 KiB
YAML
64 lines
1.3 KiB
YAML
info:
|
|
name: Register Device
|
|
type: http
|
|
seq: 1
|
|
http:
|
|
method: POST
|
|
url: '{{base_url}}/api/devices/register'
|
|
auth: none
|
|
headers:
|
|
- key: Content-Type
|
|
value: application/json
|
|
body:
|
|
type: json
|
|
data: "{\n \"device_name\": \"My Kobo Clara\",\n \"device_type\": \"kobo\",\n \"device_identifier\": \"N1234567890123\"\n}"
|
|
docs: '## Register Device
|
|
|
|
|
|
Initiates device registration by sending device information to the server.
|
|
|
|
|
|
**Method:** POST
|
|
|
|
|
|
**Endpoint:** /api/devices/register
|
|
|
|
|
|
**Authentication:** None (public endpoint)
|
|
|
|
|
|
**Request Body:**
|
|
|
|
- `device_name` (string): Human-readable name for the device
|
|
|
|
- `device_type` (string): Type of device - `kobo`, `koreader`, or `web`
|
|
|
|
- `device_identifier` (string): Unique device identifier (serial number or other ID)
|
|
|
|
|
|
**Response:**
|
|
|
|
- `registration_id` (string): UUID for tracking registration status
|
|
|
|
- `status` (string): Registration status - `pending`, `approved`, or `rejected`
|
|
|
|
- `message` (string): Status message
|
|
|
|
|
|
**Status Codes:**
|
|
|
|
- 201: Registration initiated successfully
|
|
|
|
- 400: Invalid request data
|
|
|
|
- 409: Device already registered
|
|
|
|
|
|
**Notes:**
|
|
|
|
- Device registration requires user approval before activation
|
|
|
|
- Registration ID should be stored for status checking
|
|
|
|
- Device identifier must be unique per device'
|