Skip to content
Registry StackDocsDevelopment (unreleased)

caseworkctl check command reference

View as Markdown

Validate policy, closed context schemas and required provider capabilities offline.

This page is generated from the public Clap command tree for Registry Stack source version 0.45.0 and catalog SHA-256 18546dbdf436972522108829ab0f8c804142a7474cfe3841e0b8ff10e061c842. Hidden implementation commands are omitted.

caseworkctl check [OPTIONS] <PROJECT>
ConditionRequirement
--provider-id <PROVIDER_ID> is present--against-breg-package <DIRECTORY> is required.
--environment is present--runtime-config <FILE> is required.
ArgumentAlways requiredDefaultValuesEnvironmentDescription
<PROJECT>Yesn/an/an/aExisting authored Casework project directory
OptionAlways requiredDefaultValuesEnvironmentDescription
--productionNon/an/an/aCheck the exact package closure required for production
--deny-warningsNon/an/an/aRefuse authored warnings as well as errors
--against-breg-package <DIRECTORY>Non/an/an/aCompare imported provider contracts with this sealed native Base Registry Engine (BReg) package
--provider-id <PROVIDER_ID>Non/an/an/aLimit native package comparison to this declared provider
--bregctl-bin <BINARY>Non/an/an/aMatching bregctl executable used for native package verification; otherwise use the rstack-selected helper or bregctl on PATH
--runtime-config <FILE>Non/an/an/aRuntime configuration file
--environmentNon/an/an/aResolve configured environment substitutions while checking the runtime file
--format <FORMAT>Nohumanhuman, jsonn/aWrite human diagnostics and reports, or one typed JSON report
-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.