Add view_index_matadata connector permission for fleet-server account #113262
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.
Changes
See #112556 for details.
Add permissions to fleet-server service account to enable running elastic/connectors as an integration.
Fleet service service account owns and generates api keys that are used by integrations (components) enrolled in fleet. Connectors are (soon) an integrations that can be deployed in agentless to offer Elastic-managed ingestion story.
When changing from
read,write,manage
to more granular permissions I missedview_index_metadata
.This allows the connector service to call
GET {index}
, without this permission content sync would fail. (I somehow missed that during testing of the last PR...)Validation
Tested locally with
view_index_metadata
permission added tofleet-server
service account. Performed full content sync with updated permission model.