Struct ConfigureResult 

pub struct ConfigureResult {
    pub service: String,
    pub changes: Vec<ConfigureChange>,
    pub diff: DiffResult,
    pub steps: Vec<Step>,
    pub has_destructive: bool,
}

Output of configure_service.

Fields

service: String

changes: Vec<ConfigureChange>

High-level transitions, in a stable order — the CLI walks this for the human-readable summary and the destructive-change gate.

diff: DiffResult

File-level diff from the upgrade machinery. Empty entries means no files differ from the current install (only metadata-level changes like --backup might still be in changes).

steps: Vec<Step>

Steps to execute. Empty when neither files nor metadata would change (no-op configure).

has_destructive: bool

True if at least one change in changes is destructive.

Implementations

impl ConfigureResult

pub fn is_noop(&self) -> bool

True when nothing would change at all — neither files, env, nor metadata. The CLI uses this to short-circuit “already configured that way” without printing a confusing empty summary. steps is the source of truth: [build_configure_steps] returns Vec::new() whenever no step would run.