Expand description
The set of fields each list command can emit, and validation of --fields.
These tables are the single source of truth. schema publishes them as
output_fields, and --fields validates against them, so the contract an
agent reads is exactly the contract the CLI enforces.
A --fields request naming something outside the table is a usage error.
Silently dropping it, as this once did, hands back {} per row with exit 0,
which is indistinguishable from a successful query that found nothing.
Structs§
- Invalid
Fields - A
--fieldsrequest naming one or more unknown fields.
Constants§
- CLIENTS_
LIST - CLIENTS_
SHOW - DEVICES_
LIST - EVENTS_
LIST - NETWORKS_
LIST - PORTS_
FIND ports findrows: thePORTS_LISTset plusconnected, which distinguishes a live attachment from a stale record. Kept separate fromPORTS_LISTso thedevices portsalias gains exactly two new keys.- PORTS_
LIST
Functions§
- names
- Field names of a table, in declaration order.
- validate
- Parse and validate a comma-separated
--fieldsspec against a table.
Type Aliases§
- Field
- A field name paired with its JSON type, as published in
unifi schema.