RANGER-5320:Handle unsupported cipher key creation #672
Conversation
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
dhavalshah9131
assigned
dhavalshah9131 and
ChinmayHegde24 and unassigned
dhavalshah9131
dhavalshah9131
requested review from
kishorgollapalliwar,
dhavalshah9131,
dineshkumar-yadav and
spolavarpau1
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?
Creation of key with cipher other than default supported value by KMS should fail but in actual Key was getting created successfully, So it is handled in this patch
How was this patch tested?
local mvn build test
Brought up docker containers and tested key creations in Ranger UI