opschain changes export
Included from Basic tier
opschain changes export <id|code> [-f <file>] [--owner /|/projects/<code>]
Writes the record and its whole story as NDJSON — one JSON document per
line, each with a kind: the record first (change_record), then each run
under it (run), each break-glass record (breakglass_record) and every
story entry in order (event). Actors are principal ids, never usernames
or emails; a run's own payloads stay on its run page. The export is the
evidence a reviewer reads to answer "what happened as a result of this
change". The runs and break-glass records are capped at 1000 each, as the
story's first page is; the entries are unbounded.
Against a server the command reads the server's ExportChangeRecord
stream and writes its bytes unchanged, so the file is byte-identical with
the GUI's Export of the same record (against a server without the
stream it walks the story's pages to the same bytes). In the local lane it
reads the home's store.
Flags
| Flag | Meaning |
|---|---|
-f, --file <file> | Write the NDJSON to this file instead of standard output. The export is written to <file>.partial and renamed to <file> only once it is complete; an export that fails part-way removes the partial file, leaves no <file>, and exits non-zero naming the failure. |
--owner <path> | The record's owner, / or /projects/<code> — narrows a code two owners hold; ignored for an id. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Exported. |
| 1 | Not found, or you may not read it. |