create-integration

You can automate the Elastic integration package creation by orchestrating end-to-end workflows that scaffold the structure and coordinate CEL, ingest pipelines, and system tests. This ensures consistent package topology and automates the full lifecycle.

The best way to scaffold a new Elastic integration package is to use an automated workflow that generates a standard layout and applies post-scaffold edits. This approach enforces consistent file naming, standard manifests, and reliable template generation.

Yes, the workflow orchestrates CEL, ingest pipelines, and system-test subagents together. It coordinates these components end-to-end to ensure your Elastic integration packages are built, structured, and tested consistently.

You need to orchestrate subagents for integration builds when automating the end-to-end lifecycle of Elastic integration packages. This is required for coordinating CEL, pipeline, and system-test tasks to ensure consistent templates and testing workflows.

Building Elastic integrations requires standard requirement files, manifests, and references to ensure consistent templates, naming, and testing workflows. These references guide the package topology, scaffold commands, and post-scaffold edits.

Yes, you can use this automation to apply post-scaffold edits to your package layout. It automates the end-to-end lifecycle of creating Elastic integration packages, ensuring standard file layouts and consistent package topology.