How the Integration Domain Connects to the Pipeline
The existing TransformationPipeline is untouched. The Integration Domain hooks in through two extension points: the RecordWriter interface (outbound) and a new FileIngestionService (inbound).
Current vs Extended Pipeline
New DestinationType Values
The DestinationType enum gains new values to cover all integration destinations:
PipelineRequest Changes
PipelineRequest gains a clientId and an optional deliveryIntegrationId:
Outbound Writer Resolution
Inbound File Ingestion Flow
Inbound connectors are not driven by the pipeline — they drive the pipeline. A scheduled poller pulls files and feeds them in.