Skip to content

DEV: correct ACL docs regarding prefixes #1653

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jun 4, 2025
Merged

DEV: correct ACL docs regarding prefixes #1653

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
49cc315
DEV: correct ACL docs regarding prefixes
dwdougherty Jun 3, 2025
a41da0b
Minor grammar correction.
dwdougherty Jun 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/operate/oss_and_stack/management/security/acl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -311,7 +311,7 @@ The following is a list of command categories and their meanings:
* **pubsub** - all pubsub related commands.
* **read** - Reading from keys (values or metadata). Note that commands that don't interact with keys, will not have either `read` or `write`.
* **scripting** - Scripting related.
* **search** - All search related commands. Note that indexes can only be created/modified if their key prefixes are a superset of the keys to which a user has access. For example, a user with the key ACL pattern `h:*` can create an index with keys prefixed by `h:*` or `h:p*`, but not keys prefixed by `h*`, `k:*`, or `k*`, because these prefixes may involve keys to which the user has access.
* **search** - All search related commands. Only ACL users with access to a superset of the key prefixes defined during index creation can create, modify, or read the index. For example, a user with the key ACL pattern `h:*` can create an index with keys prefixed by `h:*` or `h:p*`, but not keys prefixed by `h*`, `k:*`, or `k*`, because these prefixes may involve keys to which the user does not have access.
* **set** - Data type: all set related commands.
* **sortedset** - Data type: all sorted set related commands.
* **slow** - All commands that are not `fast`.
Expand Down