IPipelineExecutionMode
Namespace: Meshmakers.Octo.Sdk.Common.EtlDataPipeline.Execution
Carries per-execution mode flags surfaced to pipeline nodes (e.g. dry-run). Threaded onto the per-execution INodeContext by IEtlDataOrchestrator.ExecutePipelineAsync<TEtlContext>(NodeDefinitionRoot, TEtlContext, IPipelineDebugger, Object, IPipelineExecutionMode) when the caller passes a non-null instance; otherwise nodes see a null INodeContext.PipelineExecutionMode and behave as in any classic (real-effect) run. M4-B.2 only defines the dry-run flag; further mode flags can be added here without breaking the wire.
public interface IPipelineExecutionMode
Properties
IsDryRun
When true, Load nodes that honour the flag MUST suppress their real
side effect (no MongoDB write, no HTTP call, no SMTP/SFTP transmission)
and instead emit a "would-have-written" payload via
INodeContext.RecordDryRunIntent(String, Object).
Load nodes that do NOT honour the flag run for real; the executor
reports them to the caller (via LoadNodesNotHonouringDryRun in
the MCP dry_run_pipeline response) so the agent and the operator
know which side effects might have fired.
public abstract bool IsDryRun { get; }