Deploy a Clari Scheduled Data Pipeline

Overview

Deploy orchestration rather than embedding long-running polling in ephemeral request handlers. Ensure one logical scheduler owns each workload, persists provider job IDs or cursors before waiting, and separates landing from publication.

Prerequisites

• Versioned container or runtime artifact and infrastructure manifest
• Per-surface credential references and least-privilege identity
• Durable checkpoint store, encrypted landing zone, and atomic publish mechanism

Instructions

Step 1: Package the worker

Pin dependencies and contract fingerprints, run as a non-root identity, and expose no inbound endpoint unless operationally required.

Step 2: Inject configuration