Released docs. You are viewing the documentation published with v0.46.0. Development docs are available at Latest.
evidence-oid4vci check command reference
Check the runtime file offline, as serve reads it, then exit.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.0 and catalog SHA-256 d43b1bf418e0b00fac52311fa3a106fa124512dbc88cf511475713af2d73aa47. Hidden implementation commands are omitted.
Description
Section titled “Description”Check the runtime file offline, as serve reads it, then exit. Reads the one file and nothing else: no network, no socket, and no secret material. It does not prove that the client key resolves or that its JWK parses: serve or inspect proves both when it starts. Exits 0 when nothing is refused, 1 when something is refused or, under —deny-warnings, a warning is reported, 2 when the command line is invalid, and 3 when the file cannot be read.
evidence-oid4vci check [OPTIONS] --runtime-config <FILE>Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--runtime-config <FILE> | No | n/a | n/a | EVIDENCE_OID4VCI_RUNTIME_CONFIG | Runtime configuration file |
--format <FORMAT> | No | human | human, json | n/a | Emit the selected command’s report in this format |
--deny-warnings | No | n/a | n/a | n/a | Exit 1 when a warning is reported |
--environment | No | n/a | n/a | n/a | Fill ${NAME} expressions in the runtime file from the process environment and check the values they produce. Without it, each expression is checked by syntax and position only |
-h, --help | No | n/a | n/a | n/a | Print help (see a summary with ‘-h’) |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.