Bhavesh Amre created RANGER-5543:
------------------------------------
Summary: Ranger KMS GCP always try to create master key
irrespective of its existence
Key: RANGER-5543
URL: https://issues.apache.org/jira/browse/RANGER-5543
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Bhavesh Amre
Assignee: Bhavesh Amre
GCP HSM integration in Ranger KMS was failing due to missing dependencies and
repeated attempts to create an already existing master key, leading to
unnecessary exceptions and instability.
Introduced a master key existence check in the GCP HSM provider to prevent
duplicate key creation attempts.
Updated the generateMasterKey() method to handle existing keys more gracefully
and reduce redundant API calls.
Implemented a new masterKeyExists() method using GCP KMS APIs for reliable key
validation.
Added missing dependencies (Guava, failureaccess, protobuf) to ensure
compatibility with GCP libraries.
Updated KMS assembly configuration to package required dependencies correctly.
Improved dependency version management by introducing a dedicated property for
failureaccess.
Removed redundant self-referencing code and enhanced overall code clarity.
Ensured minimal and targeted code changes without impacting existing
functionality.
Improved overall stability and reliability of GCP HSM integration in Ranger KMS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
