bregctl proposal-retention dry-run command reference
Count exactly what one Proposal retention erase would remove.
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.
bregctl proposal-retention dry-run [OPTIONS] --runtime-config <ABSOLUTE_FILE> --action-id <ACTION> --proposal-id <UUID> --submission-version <VERSION>Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--runtime-config <ABSOLUTE_FILE> | Yes | n/a | n/a | n/a | Runtime configuration file. A symbolic link at any component of this path is refused. |
--action-id <ACTION> | Yes | n/a | n/a | n/a | Compiled Action identifier |
--proposal-id <UUID> | Yes | n/a | n/a | n/a | Exact Proposal UUID |
--submission-version <VERSION> | Yes | n/a | n/a | n/a | Exact proposal version to inspect or erase |
--format <FORMAT> | No | human | human, json | n/a | Emit the selected command’s report in this format |
-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.