Skip to content
Registry StackDocsv0.46.0

evidencectl dev token command reference

View as Markdown

Acquire a fresh local service token and report its private header-file path.

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.

evidencectl dev token [OPTIONS] <CLIENT> [PROJECT]
ArgumentAlways requiredDefaultValuesEnvironmentDescription
<CLIENT>Yesn/an/an/aRegistered local client ID
[PROJECT]No.n/an/aReady local project. Defaults to the current directory
OptionAlways requiredDefaultValuesEnvironmentDescription
--evidence-port <EVIDENCE_PORT>Non/an/an/aLoopback port for the local Registry Evidence service
--issuer-port <ISSUER_PORT>Non/an/an/aLoopback port for the local issuer service
--issuer-project <PROJECT>Non/an/an/aReady Base Registry Engine (BReg) dev project that owns the shared issuer and Evidence client registrations
--resource <URI>Non/an/an/aExact inbound OAuth resource for this retained Evidence session. Defaults to the local gateway resource on first start
--target <TARGET>Non/an/an/aSelect the governed target and its complete authority. Defaults to local-target.yaml
--format <FORMAT>Nohumanhuman, json, junitn/aEmit the selected command’s report in this format. junit is accepted only by test and fixtures run
-h, --helpNon/an/an/aPrint help

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.