diff options
| author | tv <tv@krebsco.de> | 2026-11-19 20:58:40 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 22:10:16 +0100 |
| commit | 59cc0283117be6b4195afbe857d702e7f8ddba6e (patch) | |
| tree | e16ca3aeddb1007eff6b5b289b95a9f562730199 /docs/openapi.yaml | |
| parent | 011560a72ca895d8b516983485cfc45c9984cd45 (diff) | |
continuum-party status: a key, a node, a party a line, nodes by their names
`status` said each party's keys and nodes in one line, separated by
commas, nodes by their IDs alone. Now each goes on a line of its own,
indented beneath its heading (party_lines): the keys the version names,
which sign votes, proposals, the key set and node list; those of the key
set as it counts, which sign writes, or `the same`; `--key`'s marked, and
said where it is none of them; and the nodes, each with the name it gave
itself (`--alias`) where it did, as the dashboard names nodes. The store
and the version are a heading each too, the parties one a line.
The names come from GET /events/counts, which gives each party's
`names` now (by node ID, of the nodes that gave themselves one), so that
a party's session, which reads no /peers, has them. Bash completion
reads the parties from the new layout.
Diffstat (limited to 'docs/openapi.yaml')
| -rw-r--r-- | docs/openapi.yaml | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 797c46f..af17d69 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -1586,7 +1586,8 @@ paths: description: | What counts, as the store reads now (docs/federation.md): the current version (its number, its hash, its revision, by number and ID and as people read it, and - the version itself), each party's keys and nodes, what each of those nodes said + the version itself), each party's keys and nodes, the names those nodes gave + themselves (`names`, by node ID, `--alias`, of those that did), what each said it speaks and knows (`knows`, by node ID: the wire versions it speaks, the oldest and the newest, and the newest revision of the federation it knows, by number and ID and as people read it, its number null where this node doesn't know it; @@ -1622,7 +1623,7 @@ paths: type: object additionalProperties: type: object - required: [keys, nodes, knows] + required: [keys, nodes, names, knows] properties: keys: type: array @@ -1632,6 +1633,10 @@ paths: type: array items: type: string + names: + type: object + additionalProperties: + type: string knows: type: object additionalProperties: |
