Released docs. You are viewing the documentation published with v0.46.0. Development docs are available at Latest.
caseworkctl provider add command reference
Create an approval project from a Base Registry Engine (BReg) Action and print missing configuration.
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.
caseworkctl provider add [OPTIONS] --breg-project <PROJECT> --action <ACTION> --pattern <PATTERN> <DIRECTORY>Constraints
Section titled “Constraints”| Condition | Requirement |
|---|---|
--package-output <DIRECTORY> is present | --breg-package <DIRECTORY> is required. |
Arguments
Section titled “Arguments”| Argument | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
<DIRECTORY> | Yes | n/a | n/a | n/a | New Casework directory, or a previously generated project to check without rewriting |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--breg-project <PROJECT> | Yes | n/a | n/a | n/a | Authored BReg project inspected through its matching bregctl executable |
--action <ACTION> | Yes | n/a | n/a | n/a | Proposal-mode BReg Action to review |
--pattern <PATTERN> | Yes | n/a | single-reviewer-approval, two-peer-approval, technical-check-then-authorization | n/a | Approval stages and outcomes shared with caseworkctl init |
--breg-package <DIRECTORY> | No | n/a | n/a | n/a | BReg deployment package to pair and compare before packaging Casework |
--package-output <DIRECTORY> | No | n/a | n/a | n/a | Package directory written with a new project; omit to inspect the package without writing it |
--bregctl-bin <BINARY> | No | n/a | n/a | n/a | Matching bregctl executable used for public project and package inspection; otherwise use the rstack-selected helper or bregctl on PATH |
--format <FORMAT> | No | human | human, json | n/a | Write human diagnostics and reports, or one typed JSON report |
-h, --help | No | n/a | n/a | n/a | Print help |
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.