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
Copy file name to clipboardexpand all lines: docs/getting-started/concepts/permission.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ The permission model is based on the following components:
36
36
The `Permission` class identifies a single permission configured on the feature store and is identified by these attributes:
37
37
-`name`: The permission name.
38
38
-`types`: The list of protected resource types. Defaults to all managed types, e.g. the `ALL_RESOURCE_TYPES` alias. All sub-classes are included in the resource match.
39
-
-`name_pattern`: A regex to match the resource name. Defaults to `None`, meaning that no name filtering is applied
39
+
-`name_patterns`: A list of regex patterns to match resource names. If any regex matches, the `Permission` policy is applied. Defaults to `[]`, meaning no name filtering is applied.
40
40
-`required_tags`: Dictionary of key-value pairs that must match the resource tags. Defaults to `None`, meaning that no tags filtering is applied.
41
41
-`actions`: The actions authorized by this permission. Defaults to `ALL_VALUES`, an alias defined in the `action` module.
42
42
-`policy`: The policy to be applied to validate a client request.
@@ -95,7 +95,7 @@ The following permission grants authorization to read the offline store of all t
95
95
Permission(
96
96
name="reader",
97
97
types=[FeatureView],
98
-
name_pattern=".*risky.*",
98
+
name_patterns=".*risky.*",# Accepts both `str` or `list[str]` types
0 commit comments