Do not check for alias when setup.ilm.check_exists is false #13848
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, setting
setup.ilm.check_exists
tofalse
only turns off checking if the ILM policy exists (GET _ilm/policy/{name}
).This would expand that to also turn off checking if an alias exists (
GET _alias/{name}
).The advantage would be that with
setup.ilm.check_exists
set tofalse
theview_index_metadata
privilege would no longer be required, leaving only themonitor
cluster privilege andcreate
index privileges as the only privileges that are always required to publish data from Beats.Instead of changing the behavior of
setup.ilm.check_exists
we could also introduce a new configuration option. I like keeping it simple though, so only a single change to the config file is necessary for minimal privileges.This is one of three PRs to reduce the Beats privileges required in code and documentation:
Relates: #10241