From 7de4b312e7f1ef3b4fa66384e2d5a3ba84c9e2ef Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Tue, 29 Jun 2021 15:37:07 -0700 Subject: [PATCH] API keys do not reflect the need for read_pipeline (#26466) (#26581) 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. Co-authored-by: Philipp Kahr --- 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}-*"],