Enum ScenarioAction 

#[non_exhaustive]
pub enum ScenarioAction {
    Send {
        to: EndpointRef,
        body: Option<Value>,
        headers: Option<BTreeMap<String, Value>>,
        method: String,
        expect_reply: Option<Expectation>,
    },
    Receive {
        from: EndpointRef,
        deadline: Duration,
        extract: Option<BTreeMap<String, String>>,
    },
    Sleep {
        duration: Duration,
    },
    Validate {
        target: ScenarioTarget,
        expectation: ValidateExpectation,
        deadline: Option<Duration>,
        elapsed_at_least: Option<Duration>,
    },
    Sql {
        datasource: String,
        prepare: Vec<String>,
    },
}

One ordered scenario action (ADR-0069 section 11, adopted from Citrus: send, receive with a mandatory deadline, sleep, validate, sql).

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Send

Send a message to an endpoint.

Fields

to: EndpointRef

Target endpoint reference.

body: Option<Value>

Message body; omitted means an empty body.

headers: Option<BTreeMap<String, Value>>

Message headers.

method: String

Resolved method: explicit or inferred (POST with a body, GET without), uppercase.

expect_reply: Option<Expectation>

Reply assertion for direct: sends (rc-qvz6): the same matcher grammar validate parses, evaluated against the synchronous route reply the context-stimulus adapter returns. Load-time rejected on every other scheme.

Receive

Receive a message from an endpoint before the deadline passes.

Fields

from: EndpointRef

Source endpoint reference.

deadline: Duration

Mandatory deadline, real monotonic time.

extract: Option<BTreeMap<String, String>>

Extractions into scenario variables, keyed by variable name.

Sleep

Pause the scenario for the given duration.

Fields

duration: Duration

Sleep length.

Validate

Assert an expectation against a scenario target.

Fields

target: ScenarioTarget

What to validate: the last message received on an endpoint, a scenario variable, a partner’s recorded traffic, or a datasource read.

expectation: ValidateExpectation

Matcher expectation: the message grammar for lastReceived and variable targets, the partner count grammar for partner targets, the sql row grammar for sql targets.

deadline: Option<Duration>

Optional poll deadline. Only valid on partner and sql targets, whose assertions settle asynchronously or read a live datasource; without it the partner assertion reads one immediate snapshot.

elapsed_at_least: Option<Duration>

Optional minimum wire-arrival age. Only valid on lastReceived targets: the last received message must have arrived at least this long after the scenario started (the not-before-X control run.sh expresses with awk). The assertion anchors to the message’s wire arrival, never the consumption time.

Sql

Seed datasource state before the route assertions run (bd rc-25lup.1): execute the ordered prepare mutation statements against the named datasource’s pool through the scenario sql: vocabulary. Reads are rejected at load (is_read_statement): the validate sql target owns reads, and the two vocabularies never mix. Activation is demand-gated behind the harness sql feature (the inbound:/http precedent, ADR-0069 §8); the grammar and validation run in every build.

Fields

datasource: String

The datasource name as declared under [datasources.*] in Camel.toml.

prepare: Vec<String>

Ordered SQL mutation statements, executed in order against the datasource’s pool.

Trait Implementations

impl Clone for ScenarioAction

fn clone(&self) -> ScenarioAction

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ScenarioAction

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

Formats the value using the given formatter.