LiJie20190102 commented on PR #13500: URL: https://github.com/apache/gravitino/pull/13500#issuecomment-6071291432
> @LiJie20190102 Could it be possible to implement it using the existing secretManager feature of gravitino instead? Yes, that's exactly the direction — see my earlier reply above (https://github.com/apache/gravitino/pull/13500#issuecomment-5854417884). The plan is to reuse the existing `SecretProvider` SPI: add a built-in `FileSecretsProvider` (encrypted keystore file), keep `SecretManager`/`SecretUrn`/ `SecretProviderRegistry` untouched, and resolve config values via a small `ConfigSecretResolver` at the three JDBC password read sites. Plaintext values pass through unchanged for backward compatibility. @jerryshao already confirmed the approach generally looks OK. Waiting for your detailed review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
