Skip to content
Registry StackDocsv0.38.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.38.0 and catalog SHA-256 cd13c658f65af295f9df3c6db86dc045ac06e9e040afc1f5f5b27c3184ab653d. 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 Evidence Gateway 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/aReuse a local target’s source connections and outbound TLS in the generated local caller rehearsal. Target service authentication is not replayed
--format <output_format>Nohumanhuman, json, junitn/aSelect human-readable or machine-readable output. junit is accepted only by fixture runs (test and fixtures run)
-h, --helpNon/an/an/aPrint help

Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.