Expand description
rk adopt: a pre-record target becomes a recorded one.
Adoption verifies the payload before writing configuration and its record. The
candidate payload is rendered first, exactly as rk init would
produce it; every rendered destination must match it byte for byte,
and one mismatch refuses the whole adoption listing every mismatch in
one run. Blessing whatever is on disk would launder arbitrary drift
into release-kit ownership, so nothing here ever takes the disk as the
baseline — and no target file is ever changed: not a byte, not a mode,
not a sentinel. Configuration writes before the manifest, after every check
has passed.
Functions§
- run
- Verify the target against the rendered candidate and, on
--apply, write the config and record inside.release-kit/.