Use less restrictive API to check if template exists #13847
Merged
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.
Switches from using
HEAD _template/{name}
toGET _cat/templates/{name}
to check if a template exists before trying to load it.The significance is that the
_cat/templates
API requires only themonitor
cluster privilege and not the far more permissivemanage_index_templates
. With this change, the default Beats configuration works without any unnecessary write privileges for publishing. (Note: The documentation recommended settingsetup.template.enabled
tofalse
which turns off the template check completely.)This is one of three PRs to reduce the Beats privileges required in code and documentation:
Relates: #10241