Struct ScenarioDocument 

pub struct ScenarioDocument {
    pub source_path: PathBuf,
    pub route_source: RouteSource,
    pub scenario: Vec<ScenarioAction>,
    pub partners: Option<BTreeMap<String, Vec<PartnerScript>>>,
    pub env: Option<BTreeMap<String, String>>,
    pub env_passthrough: Option<Vec<String>>,
    pub profile: Option<String>,
    pub send_deadline: Option<Duration>,
    pub inbound: Option<InboundListener>,
    pub logs: Option<LogsAssertion>,
}

A parsed scenario document. Route file paths stay as declared; resolving them against the document directory or the project root is the runner’s job, the same split the unit-tier parser keeps.

Fields

source_path: PathBuf

The document’s own path as parsed. The boot root may be a nearest-ancestor Camel.toml directory rather than the document’s directory, so the document directory travels with the model: relative routeFiles anchor here (rc-jjzy5).

route_source: RouteSource

The single declared route source.

scenario: Vec<ScenarioAction>

Ordered scenario actions.

partners: Option<BTreeMap<String, Vec<PartnerScript>>>

Document-level partner scripting, keyed by endpoint address. The grammar lives here; the runner consumes the map.

env: Option<BTreeMap<String, String>>

Fixed fixture values for the scenario; the layered environment source reads these before any ambient value.

env_passthrough: Option<Vec<String>>

Ambient variable names allowed to pass through to the scenario.

profile: Option<String>

Profile pinned per document; an ambient profile would break hermeticity.

send_deadline: Option<Duration>

Document-level bound for every send action (rc-tr4w): an optional tighter deadline than the runner’s thirty-second default, real time only (ADR-0069 §6).

inbound: Option<InboundListener>

The document-level inbound: declaration (rc-5yon): the harness binds 127.0.0.1:0, stages the listener on the HTTP component’s global registry (ADR-0070), and exposes the bound address under the named bind variable so route URIs interpolate it. Provisioning runs behind the http feature; a declaration in a build without the feature is a named load error (ADR-0069 §8 demand-gated activation).

logs: Option<LogsAssertion>

The document-level logs: assertion block (rc-tdgh5): optional; when present, the runner opens a capture window at document start and evaluates the clauses against the captured events after the action loop. Requires the harness’s capture subscriber to own the process’s tracing seat (first-wins try_init before the boot); otherwise the document fails through the apparatus class.

Trait Implementations

impl Debug for ScenarioDocument

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.