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.
Is your feature request related to a problem? Please describe.
As of today RBAC permissions can match resources by type and a single
name_patternfield, as in: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: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_patternfield for backward compatibility.