Skip to content
Registry StackDocsv0.46.0

registry-render check command reference

View as Markdown

Check a bundle or package and a runtime file offline, reporting every finding.

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.

Check a bundle or package and a runtime file offline, reporting every finding. 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 an input cannot be read.

registry-render check [OPTIONS]
ConditionRequirement
--environment is present--runtime-config <FILE> is required.
--require-audit-under <ABSOLUTE_DIRECTORY> is present--runtime-config <FILE> is required.
OptionAlways requiredDefaultValuesEnvironmentDescription
--bundle <BUNDLE>Non/an/an/aAuthored bundle or package directory (default: the current directory, unless only —runtime-config is given)
--runtime-config <FILE>Non/an/an/aRuntime configuration file
--environmentNon/an/an/aFill ${NAME} expressions in the runtime file from the process environment and check the values they produce, reading each seal’s certificate chain file too (never its key). Without it, each expression is checked by syntax and position only, and no chain file is read
--require-audit-under <ABSOLUTE_DIRECTORY>Non/an/an/aProve that the runtime file’s audit file resolves under this absolute directory, the one the deployment mounts as persistent storage. A stdout audit destination is refused. Requires —runtime-config
--format <FORMAT>Nohumanhuman, jsonn/aEmit the selected command’s report in this format
--deny-warningsNon/an/an/aExit 1 when a warning is reported
-h, --helpNon/an/an/aPrint help (see a summary with ‘-h’)

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.