TriggerContext
Namespace: Meshmakers.Octo.Sdk.Common.EtlDataPipeline
Implementation of the extract node context
public abstract class TriggerContext : ITriggerContext
Inheritance Object → TriggerContext
Implements ITriggerContext
Properties
NodeContext
public INodeContext NodeContext { get; }
Property Value
GlobalConfiguration
public IGlobalConfiguration GlobalConfiguration { get; }
Property Value
TenantId
public string TenantId { get; }
Property Value
DataFlowRtId
public OctoObjectId DataFlowRtId { get; }
Property Value
OctoObjectId
PipelineRtEntityId
public RtEntityId PipelineRtEntityId { get; }
Property Value
RtEntityId
Methods
ExecuteAsync(ExecutePipelineOptions, Object)
public Task<object> ExecuteAsync(ExecutePipelineOptions executePipelineOptions, object input)
Parameters
executePipelineOptions ExecutePipelineOptions
input Object
Returns
StartExecutePipelineAsync(ExecutePipelineOptions, Object)
public abstract Task<Guid> StartExecutePipelineAsync(ExecutePipelineOptions executePipelineOptions, object value)
Parameters
executePipelineOptions ExecutePipelineOptions
value Object
Returns
EndExecutePipelineAsync(Guid)
public abstract Task<object> EndExecutePipelineAsync(Guid pipelineExecutionId)
Parameters
pipelineExecutionId Guid
Returns
ReportStatusAsync(String, Boolean, CancellationToken)
public Task ReportStatusAsync(string message, bool isError, CancellationToken cancellationToken)
Parameters
message String
isError Boolean
cancellationToken CancellationToken
Returns
Remarks:
A no-op here, deliberately virtual rather than abstract: the base is subclassed outside this repository (the mesh adapter keeps a hand-maintained copy of the SDK's trigger context), and a status line nobody delivers is harmless, whereas an abstract member would break every such subclass on the package update. The hosts that own an IPipelineExecutionReporter override it.