bregctl apply command reference

Apply one built package using the configured migration authority.

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.

Usage

bregctl apply [OPTIONS] --runtime-config <ABSOLUTE_FILE> --package <ABSOLUTE_DIRECTORY>

Options

Option	Always required	Repeatable	Default	Values	Environment	Description
--runtime-config <ABSOLUTE_FILE>	Yes	No	n/a	n/a	n/a	Runtime configuration file. A symbolic link at any component of this path is refused.
--package <ABSOLUTE_DIRECTORY>	Yes	No	n/a	n/a	n/a	Absolute target package directory. A symbolic link at any component of this path is refused.
--initial	No	No	n/a	n/a	n/a	Activate the first package in an uninitialized Registry database
--backup <BINDING_PATH=BINDING_FILE>	No	Yes	n/a	n/a	n/a	Reviewed backup binding the plan requires and the absolute backup binding file that satisfies it, as BINDING_PATH=BINDING_FILE
--operator-reference <REFERENCE>	No	No	n/a	n/a	n/a	Operator change reference, at most 512 bytes, recorded as a keyed hash in the activation ledger and audit
--expected-digest <SHA256_DIGEST>	No	No	n/a	n/a	n/a	Package digest the target package must have, as plan and package print it; apply refuses another package before any database contact
--format <FORMAT>	No	No	human	human, json	n/a	Emit the selected command’s report in this format
-h, --help	No	No	n/a	n/a	n/a	Print help

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.