You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add CONNECTOR resource type for granular connector-level permissions
- Add CONNECTOR to supported resource types
- Document connector actions and value format (connectName/connectorName)
- Add examples for specific connector and wildcard permissions
- Remove outdated "connectors selector not implemented yet" comment
Copy file name to clipboardExpand all lines: configuration/rbac-role-based-access-control/README.md
+13-7Lines changed: 13 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ Find the more detailed examples in a full example file lower.
99
99
100
100
The next thing which is present in your roles file is, surprisingly, permissions. They consist of:
101
101
102
-
1. Resource Can be one of the: `CLUSTERCONFIG`, `TOPIC`, `CONSUMER`, `SCHEMA`, `CONNECT`, `KSQL`, `ACL`.
102
+
1. Resource Can be one of the: `CLUSTERCONFIG`, `TOPIC`, `CONSUMER`, `SCHEMA`, `CONNECT`, `CONNECTOR`, `KSQL`, `ACL`.
103
103
2. The resource value is either a fixed string or a regular expression identifying a resource. Value is not applicable to `clusterconfig` and `ksql` resources. Please do not fill it out.
104
104
3. Actions It's a list of actions (the possible values depend on the resource, see the lists below) that will be applied to the certain permission. Also, note, there's a special action for any of the resources called "all", it will virtually grant all the actions within the corresponding resource. An example for enabling viewing and creating topics whose name start with "derp":
105
105
@@ -119,7 +119,8 @@ A list of all the actions for the corresponding resources (please note neither r
0 commit comments