[#5336] feat(auth-ranger): Remove MANAGED_BY_GRAVITINO limit #5343
Conversation
This file contains 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.
What changes were proposed in this pull request?
Currently, Gravitino only operation have
MANAGED_BY_GRAVITINOlabel's Ranger Policy.If a user has a Ranger service and this Ranger already has some Ranger Policy.
When Gravitino will push down a Ranger Policy, if this Policy manage resource already exist in the Ranger service and this Policy doesn't have
MANAGED_BY_GRAVITINOlabel, then Gravitino will throw exception.Why are the changes needed?
Fix: #5336
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
Added ITs