Normalize JSON and JSONL output
This commit is contained in:
parent
3c84713472
commit
116a431a12
5 changed files with 276 additions and 191 deletions
|
|
@ -72,6 +72,13 @@ Most non-daemon commands talk to the daemon through a local Unix socket at
|
|||
durability settings, Iroh endpoint/relay/discovery state, and native backend
|
||||
health for automation.
|
||||
|
||||
For automation, `--json` emits one pretty JSON document and `--jsonl` emits one
|
||||
compact physical line per result. They are mutually exclusive; both success
|
||||
and error objects carry a stable top-level `type`, and machine-mode failures
|
||||
exit nonzero without mixing human prose into stdout. The detailed compatibility
|
||||
contract and examples are in [`docs/compatibility.md`](docs/compatibility.md)
|
||||
and [`docs/automation-examples.md`](docs/automation-examples.md).
|
||||
|
||||
`geth init --admin-key <public-key> --signing-key <private-key> --node-name
|
||||
<name>` records an owner/admin keychain, the local user/device/node binding, and
|
||||
signs canonical keychain payloads through `ssh-keygen -Y sign` using the
|
||||
|
|
|
|||
Loading…
Reference in a new issue