From e251a9067a5186cba299bda7f02590ba16093b63 Mon Sep 17 00:00:00 2001 From: Philipp Kahr Date: Thu, 24 Jun 2021 11:31:31 +0200 Subject: [PATCH] API keys do not reflect the need for read_pipeline As discussed in the PR https://github.com/elastic/beats/pull/26465 the docs should reflect that read_pipeline is needed when using modules. Users usually just copy and paste the JSON payload and might experience failures when running any beat with modules. --- libbeat/docs/security/api-keys.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libbeat/docs/security/api-keys.asciidoc b/libbeat/docs/security/api-keys.asciidoc index aa397ff5fee..1a934b67ce8 100644 --- a/libbeat/docs/security/api-keys.asciidoc +++ b/libbeat/docs/security/api-keys.asciidoc @@ -29,7 +29,7 @@ POST /_security/api_key "name": "{beat_default_index_prefix}_host001", <1> "role_descriptors": { "{beat_default_index_prefix}_writer": { <2> - "cluster": ["monitor", "read_ilm"], + "cluster": ["monitor", "read_ilm", "read_pipeline"], "index": [ { "names": ["{beat_default_index_prefix}-*"],