stack es ingest put-pipeline cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack es ingest put-pipeline --id <id> [options]
Create or update a pipeline.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--idstringrequired- ID of the ingest pipeline to create or update.
--master-timeoutstring- Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.
--timeoutstring- Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error.
--if-versionnumber- Required version for optimistic concurrency control for pipeline updates
--metastring- Optional metadata about the ingest pipeline. May have any contents. This map is not automatically generated by Elasticsearch.
--descriptionstring- Description of the ingest pipeline.
--on-failurestring[]-
Processors to run immediately after a processor failure. Each processor supports a processor-level
on_failurevalue. If a processor without anon_failurevalue fails, Elasticsearch uses this pipeline-level parameter as a fallback. The processors in this parameter run sequentially in the order specified. Elasticsearch will not attempt to run the pipeline's remaining processors.Repeatable: pass
--on-failuremultiple times to supply more than one value --processorsstring[]-
Processors used to perform transformations on documents before indexing. Processors run sequentially in the order specified.
Repeatable: pass
--processorsmultiple times to supply more than one value --versionnumber- Version number used by external systems to track ingest pipelines. This parameter is intended for external systems only. Elasticsearch does not use or validate pipeline version numbers.
--deprecated- Marks this ingest pipeline as deprecated. When a deprecated ingest pipeline is referenced as the default or final pipeline when creating or updating a non-deprecated index template, Elasticsearch will emit a deprecation warning.
--field-access-patternenum-
Controls how processors in this pipeline should read and write data on a document's source.
Values: classic, flexible
--error-trace- When set to
trueElasticsearch will include the full stack trace of errors when they occur. --filter-pathstring-
Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.
Repeatable: pass
--filter-pathmultiple times to supply more than one value --human- When set to
truewill return statistics in a format suitable for humans. For example"exists_time": "1h"for humans and"exists_time_in_millis": 3600000for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines. --pretty- If set to
truethe returned JSON will be "pretty-formatted". Only use this option for debugging only. --input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON