stack es indices put-template cli command

elastic stack es indices put-template --name <name> [options]
		

Create or update a legacy index template.

Behaviour flags:

--dry-run — validate all inputs and exit without performing any action

--name string required

The name of the template

--create

If true, this request cannot replace or update existing index templates.

--master-timeout string

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.

--order number

Order in which Elasticsearch applies this template if index matches multiple templates. Templates with lower 'order' values are merged first. Templates with higher 'order' values are merged later, overriding templates with lower values.

--cause string

User defined reason for creating or updating the index template

--aliases string

Aliases for the index.

--index-patterns string

Array of wildcard expressions used to match the names of indices during creation.

Repeatable: pass --index-patterns multiple times to supply more than one value

--mappings string

Mapping for fields in the index.

--settings string

Configuration options for the index.

--version number

Version number used to manage index templates externally. This number is not automatically generated by Elasticsearch. To unset a version, replace the template without specifying one.

--error-trace

When set to true Elasticsearch will include the full stack trace of errors when they occur.

--filter-path string

Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.

Repeatable: pass --filter-path multiple times to supply more than one value

--human

When set to true will return statistics in a format suitable for humans. For example "exists_time": "1h" for humans and "exists_time_in_millis": 3600000 for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines.

--pretty

If set to true the returned JSON will be "pretty-formatted". Only use this option for debugging only.

--input-file string

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)

--json

output as JSON