`maqpna keys inventory`

List the signing keys a gateway and broker use, with algorithm and post-quantum readiness

Operate-o json | yaml

Synopsis#

maqpna keys inventory [--config gateway.json] [--broker-key FILE] [--broker-pq-key FILE] [--resolve] [KEY...]

Description#

From the help of maqpna keys:

Common flags: --dry-run (print the plan only), --timeout (per rollout, default 5m), --gateway URL (used to confirm the result through the admin API when reachable). Deployments default to the chart names (maqpna-identity, maqpna-gateway, maqpna-attest, maqpna-operator); override with --deployment / --operator-deployment. See docs/runbooks/key-rotation.md.

Flags#

Flag	Type	Description	Default
`--broker-key`	string	the identity broker's -key file	none
`--broker-pq-key`	string	the identity broker's -pq-key file	none
`--config`	string	gateway.json to read the keys from	none
`--resolve`	switch	ask KMS/HSM backends for their key's algorithm (network calls)	none

The global flags (--context, -o, --no-color, ...) work with every command.

What happens when you run it#

Prints a table by default; -o json or -o yaml print the data, and --jq EXPR filters the JSON.

Exit codes#

Code	Meaning
`0`	success
`1`	error (the message says what failed, with a hint when there is one)
`2`	usage error: unknown flag, missing argument or bad value; the synopsis is printed
`3`	a check failed, a change is blocked, or a result did not match (tamper, policy mismatch) (not used by this command)

maqpna keys inventory