Repository navigation
Permission should support multiple name patterns #4510
Description
Is your feature request related to a problem? Please describe.
As of today RBAC permissions can match resources by type and a single name_pattern field, as in:
Permission(
name="reader",
types=[FeatureView],
name_pattern=".*risky.*",
policy=RoleBasedPolicy(roles=["trusted"]),
actions=[AuthzedAction.QUERY_OFFLINE],
)We should extend this concept by allowing multiple patterns instead, to simplify the customer configuration.
Describe the solution you'd like
Support a list of name_patterns instead:
Permission(
name="reader",
types=[FeatureView],
name_pattern=[".*risky.*", "critical_data"],
policy=RoleBasedPolicy(roles=["trusted"]),
actions=[AuthzedAction.QUERY_OFFLINE],
)In this case, the permission would apply to all the feature views matching any of the configured patterns.
Describe alternatives you've considered
Do not rename the name_pattern field for backward compatibility.
Activity
dmartinol commentedon Sep 10, 2024
@franciscojavierarceo
franciscojavierarceo commentedon Oct 15, 2024
@dmartinol do you think we could do this before I cut the next release?
dmartinol commentedon Oct 16, 2024
on it
dmartinol commentedon Oct 16, 2024
Since we haven't released any RBAC version yet, I would also rename it to plural
name_patterns