Add RFC: Fine-grained sub-resource permissions - #32
Open
rrrkharse wants to merge 1 commit into
Open
Conversation
Propose making all DB-indexed resource types independently permissionable behind a configuration flag. In simplified mode (default), behavior is identical to today. In fine-grained mode, admins can grant on run, trace, assessment, logged_model, model_version, and other sub-resources independently. Key use cases: - Run access without experiment management (#11496) - Assessment-only write access (evaluation boundary) - Model version lifecycle separation from registered_model
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Proposes making all DB-indexed resource types independently permissionable behind a configuration flag (
permission_granularity = simplified | fine_grained).Problem: MLflow's RBAC recognizes only top-level resource types (experiment, registered_model, etc.). Sub-resources (runs, traces, assessments, logged models, model versions) inherit permissions from their parent — there is no way to grant different access levels on runs vs traces vs assessments within the same experiment.
Solution: A two-mode configuration:
simplified(default): today's behavior, fully backward compatiblefine_grained(opt-in): all sub-resource types become independently permissionableKey use cases:
Design highlights:
resolve_resource()helper per validator — minimal code changeRelated: mlflow/mlflow#11496