Expand description
Offline, recoverable authenticated installation (design §S5, audit remediation F05).
install_bundle turns an offline import into a real installation:
- The input is authenticated under the configured trust policy — always, even when the config permits unauthenticated demo serving — and validated against the supported serving profile. The destination is resolved from the selected CA label, never from a filename.
- Existing state is opened strictly; rollback and predecessor continuity are checked; changes are staged while retaining other labels’ committed snapshots.
- The new immutable snapshot is written and fsynced, then the descriptor (marks + snapshot references) is committed atomically. That descriptor commit is the installation commit point.
- The configured bundle path is published atomically after the commit.
If this convenience-path update fails, the result is still committed
and carries a
publication_warning— never an error falsely claiming no installation happened. Startup recovers from the committed snapshot; retrying the identical import repairs the path.
A failure before the descriptor commit leaves the old marks and the
configured files intact. If the descriptor rename succeeds but its
directory fsync fails, the outcome is indeterminate and is reported as
CoreError::DurabilityUncertain instructing the operator to stop and
reopen state — never as a claimed rollback. There is no two-file
pseudo-transaction and no deletion of old recovery material before
commitment.
Structs§
- Install
Result - The outcome of a successful
install_bundle.
Functions§
- install_
bundle - Install an authenticated bundle for
labelinto its configured destination, following the §S5 commit order.