Struct ConfigCommit 

pub struct ConfigCommit { /* private fields */ }

One admitted, serialized config write.

Owns the process-wide writer guard and the generation write lease from admission until the commit completes (or the value drops before dispatch, which abandons preparation and releases both). Created only through LiveConfigAuthority::begin_config_commit.

The intended writer shape is: current_config() → stage a mutated clone → next_revision() (checked, before any irreversible I/O) → run persistence → publish() the committed candidate under the allocated revision. To make the irreversible phase uncancellable, move this value into a detached task (see spawn_agent_lifecycle_job) before the first persistence await; the task then owns serialization and drain accounting until it finishes, and a dropped requester cannot strand a committed disk write without its publication.

Implementations

impl ConfigCommit

pub fn current_config(&self) -> Config

Clone the currently published config. Read-for-modify under this commit’s serialization: no other admitted writer can interleave.

pub fn published_revision(&self) -> ConfigRevision

The revision currently published.

pub fn next_revision(&self) -> Result<ConfigRevision, ConfigCommitError>

Allocate the next publication identity, checking representability. Call before any irreversible persistence: an exhausted epoch must refuse the commit while disk state is still unchanged.

pub fn publish( &self, revision: ConfigRevision, config: Config, ) -> Result<(), ConfigCommitError>

Publish one committed candidate under its pre-allocated revision. Installs the config and revision as one pair; refuses a revision that is not the exact successor of the published one.

pub fn live_handle(&self) -> LiveConfigHandle

Read-only live handle over the storage this commit publishes to, for post-commit reads.

pub fn release_serialization(self)

Release serialization explicitly — the writer guard and the generation write lease drop here — while the caller continues with slow, non-config side effects. The retained destructive transactions call this after their required config work, exactly where they previously dropped the raw writer guard before workspace cleanup.