Open
Conversation
✅ Deploy Preview for thriving-cassata-78ae72 canceled.
|
304f479 to
8dadf14
Compare
4900aef to
e4c0d4b
Compare
e4c0d4b to
d991e35
Compare
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
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
This implements the first phase of the RBAC migration strategy from issue #1575. When namespaces are created, we now automatically create owner roles and assign them to the creator.
This prepares the codebase for RBAC without changing current behavior. Since
default_access_policy = "permissive", existing access patterns remain unchanged - everyone can still access everything. The roles are simply "staged" in the database for when RBAC enforcement is enabled.Test Plan
make checkpassesmake testshows 100% unit test coverageDeployment Plan