elastic-package-cli

To validate an Elastic integration package, run the elastic-package format, lint, check, and build commands in sequence to enforce package structure and quality. This automated validation ensures consistent formatting and packaging for local development and CI workflows.

You can run system tests for an Elastic integration by using the elastic-package stack and service commands to manage a local Elastic stack lifecycle. Execute the test command to perform pipeline and system tests for end-to-end validation.

The best way to automate Elastic integration formatting and linting in CI is to integrate the elastic-package build, check, lint, and format commands into your pipeline. This centralizes validation tasks to automatically validate packages before release.

Yes, you need the elastic-package CLI installed in your PATH to build and test Elastic integrations. You must run the commands from a package directory or use the -C flag to target a specific package directory.

To benchmark an Elastic integration package, use the elastic-package benchmark command provided by the CLI. This allows you to measure performance as part of the local development and validation lifecycle stages.