RANGER-5543:Ranger KMS GCP always try to create master key irrespective of its existence#910
Open
bhaveshamre wants to merge 1 commit intoapache:masterfrom
Open
RANGER-5543:Ranger KMS GCP always try to create master key irrespective of its existence#910bhaveshamre wants to merge 1 commit intoapache:masterfrom
bhaveshamre wants to merge 1 commit intoapache:masterfrom
Conversation
…ve of its existence
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.
What changes were proposed in this pull request?
Added missing dependencies (guava, failureaccess, protobuf-java)
Fixed unnecessary master key creation by introducing masterKeyExists()
Implemented role-based logic:
Owner → creates key only if not exists
Viewer → only checks existence, no creation
How was this patch tested?
Built successfully using mvn clean compile package install. Manual testing was performed across multiple scenarios: when using the Owner role with a new key, the key was created successfully; with an existing key, no creation was attempted. For the Viewer role, the system correctly performed only existence checks for an existing key without attempting creation, and for a new key, no creation was attempted, resulting in a permission denied error as expected.