pub struct Step {
pub id: String,
pub title: String,
pub status: Status,
pub detail: String,
pub remedy: Option<Remedy>,
pub optional: bool,
}Expand description
One thing a new install might still need.
Fields§
§id: StringStable slug, so --json output can be matched on.
title: String§status: Status§detail: String§remedy: Option<Remedy>Optional because plenty of steps are somebody else’s to do — picking a model, deciding whether they want mail at all.
optional: boolMay the owner say they never want this?
A property of the step, not of its status, and the distinction is
load-bearing: inferring it from Missing made “a provider that can
answer” declinable, so a person could decline the one thing without
which nothing runs and be told Nothing outstanding. on an install
that could not answer a single prompt. Found by running the flow
rather than by reading it.
True only where “I don’t want this” is a coherent sentence — the integrations, and the charter. Never for a credential, a server that disagrees with its config, or anything else that is the machine being wrong rather than a feature going unused.