Loading

stack es security clone-api-key cli command

Auth required
elastic stack es security clone-api-key --api-key <api-key> [options]
		

Clone an API key.

Behaviour flags:

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

--api-key string required
The credentials of the API key to clone. This is the secret value returned when the key was originally created.
--refresh enum

If true (the default) then refresh the affected shards to make this operation visible to search, if wait_for then wait for a refresh to make this operation visible to search, if false then do nothing with refreshes.

Values: true, false, wait_for

--name string
A name for the cloned API key. If not provided, the name of the source key is used.
--expiration string
The expiration time for the cloned API key. By default, API keys never expire. Set to null to explicitly create a key with no expiration.
--metadata string
Arbitrary metadata to associate with the cloned API key. It supports nested data structure. Within the metadata object, keys beginning with _ are reserved for system usage.
--[no-]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

--[no-]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.
--[no-]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
--[no-]dry-run
validate all inputs and exit without performing any action (preview changes without applying them)
--[no-]json

output as JSON