FromExecutePipelineCommandNodeConfiguration

Namespace: Meshmakers.Octo.Sdk.Common.EtlDataPipeline.Nodes.Triggers

Configuration for node FromExecutePipelineCommand

public record FromExecutePipelineCommandNodeConfiguration : TriggerNodeConfiguration, INodeConfiguration, IEquatable<NodeConfiguration>, ITriggerNodeConfiguration, IEquatable<TriggerNodeConfiguration>, IEquatable<FromExecutePipelineCommandNodeConfiguration>

Inheritance Object → NodeConfiguration → TriggerNodeConfiguration → FromExecutePipelineCommandNodeConfiguration
Implements INodeConfiguration, IEquatable<NodeConfiguration>, ITriggerNodeConfiguration, IEquatable<TriggerNodeConfiguration>, IEquatable<FromExecutePipelineCommandNodeConfiguration>

Properties

CallerBinding

How this trigger turns the sender of the trigger into the execution's verified caller (AB#5126). The three-state policy — anonymous allowed / binding optional / binding required — that makes running anonymous a deliberate choice rather than an accident of whether a channel happened to resolve a caller.

public CallerBindingMode CallerBinding { get; set; }

Property Value

CallerBindingMode

Remarks:

🟢 Additive & migration-safe. The default, CallerBindingMode.AnonymousAllowed (value 0), reproduces the pre-AB#5126 behaviour byte for byte: no directory lookup is attempted and a caller that is already present on the execution is still honoured, so a pipeline authored before this property existed keeps running unchanged.

Only triggers that carry a sender identity — the channel triggers (Teams, Signal, e-mail) and FromExecutePipelineCommand — honour this property. Internal / event / polling triggers (FromPipelineDataEvent, FromWatchRtEntity, FromPolling, …) have no sender and ignore it. FromHttpRequest@2 keeps its own pre-existing bearer model (AllowAnonymous / RequiredRoles); its caller is already carried onto the execution.

Description

Gets or sets an optional description

public string Description { get; set; }

Property Value

String

Constructors