bregctl request-retention erase command reference
Erase eligible payload detail for one exact request proposal version.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.30.0 and catalog SHA-256 2221f17eae216048d4cfaf7f66e3dcd68a250f6f6de4e24b177441819192b475. Hidden implementation commands are omitted.
bregctl request-retention erase [OPTIONS] --runtime-config <ABSOLUTE_FILE> --request-entity <ENTITY> --request-id <UUID> --proposal-version <VERSION>Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--runtime-config <ABSOLUTE_FILE> | Yes | n/a | n/a | n/a | Absolute Base Registry Engine runtime configuration file. A symbolic link at any component of this path is refused. |
--request-entity <ENTITY> | Yes | n/a | n/a | n/a | Compiled change-request entity identifier |
--request-id <UUID> | Yes | n/a | n/a | n/a | Exact request record UUID |
--proposal-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”Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.