bregctl field-encryption preflight command reference
Report what one reviewed backfill apply would do, before running it: value-free counts per covered field, the descriptor’s explicit history choice, and the record names a unique blind index would refuse.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.
bregctl field-encryption preflight [OPTIONS] --runtime-config <ABSOLUTE_FILE> --package <ABSOLUTE_DIRECTORY>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. |
--package <ABSOLUTE_DIRECTORY> | Yes | n/a | n/a | n/a | Absolute directory of the verified successor package the operator plans to apply. A symbolic link at any component of this path is refused. |
--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.