cel-programs

CEL programs for Elastic integrations are developed using a structured, end-to-end workflow that includes mock-first testing, mito validation, and seamless template wrapping into cel.yml.hbs and manifests.

You validate a CEL program with mito by following the mandated mock-first workflow: build a mock with elastic/stream, then validate the program against the running mock server phase by phase.

To wrap a validated CEL program into cel.yml.hbs, you embed the validated program into the template and configure the data stream manifest to complete the Elastic integration.

CEL handles nested state management and pagination patterns by mapping API interactions to CEL constructs with compliance to incremental phase steps, 2-level HTTP nesting, and correct event and output handling.

Yes, you need the elastic/stream mock server to follow the mandated mock-first testing workflow, allowing you to validate your CEL program with mito phase by phase before template wrapping.

The best way to develop CEL-based data collection integrations is using a structured workflow from skeleton to mito to template, ensuring guided mock-first testing and clear guidance for manifest configuration.