-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS] Adds read_ccr and manage_ccr privileges #149
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,6 +29,12 @@ This includes snapshotting, updating settings, and rerouting. It also includes | |
obtaining snapshot and restore status. This privilege does not include the | ||
ability to manage security. | ||
|
||
`manage_ccr`:: | ||
All {ccr} operations related to managing follower indices and auto-follow | ||
patterns. It also includes the authority to grant the privileges necessary to | ||
manage follower indices and auto-follow patterns. This privilege is necessary | ||
only on clusters that contain follower indices. | ||
|
||
`manage_index_templates`:: | ||
All operations on index templates. | ||
|
||
|
@@ -62,6 +68,12 @@ who created or updated them. | |
|
||
-- | ||
|
||
`read_ccr`:: | ||
All read only {ccr} operations, such as getting information about indices and | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would highlight that this cluster level privilege only needs to be configured in the leader cluster. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks, I've added that info in this PR. |
||
metadata for leader indices in the cluster. It also includes the authority to | ||
check whether users have the appropriate privileges to follow leader indices. | ||
This privilege is necessary only on clusters that contain leader indices. | ||
|
||
`transport_client`:: | ||
All privileges necessary for a transport client to connect. Required by the remote | ||
cluster to enable <<cross-cluster-configuring,Cross Cluster Search>>. | ||
|
@@ -82,6 +94,11 @@ All `monitor` privileges plus index administration (aliases, analyze, cache clea | |
close, delete, exists, flush, mapping, open, force merge, refresh, settings, | ||
search shards, templates, validate). | ||
|
||
`manage_follow_index`:: | ||
All actions that are required to manage the lifecycle of a follower index, which | ||
includes creating a follower index, closing it, and converting it to a regular | ||
index. This privilege is necessary only on clusters that contain follower indices. | ||
|
||
`view_index_metadata`:: | ||
Read-only access to index metadata (aliases, aliases exists, get index, exists, field mappings, | ||
mappings, search shards, type exists, validate, warmers, settings). This | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would highlight that this cluster level privilege only needs to be configured in the follower cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I've added that info too!