Use SecretsResolver from Airlift#22633
Conversation
bf916fa to
825b41c
Compare
825b41c to
168119d
Compare
168119d to
e4b153a
Compare
kokosing
left a comment
There was a problem hiding this comment.
The change is very straightforward. It is nice you have added product tests, but maybe more integration tests would be nice to make sure that other things work too. Consider system access control, group provider...
There was a problem hiding this comment.
you can add some REAMDE file next to credential.jckes so one would know how to recreate it, just in case
We are using them as a part of |
6db0ac0 to
fa44c20
Compare
fa44c20 to
0eadaf3
Compare
|
@kokosing Based on your review comments - Have migrated the keystore file creation to a script which would be generated in the runtime and have also tested it for config.properties, password-authenticator and connector.properties - These are the modules which are tested in our ProductTest and for other modules we might need to increase the test coverage in an incremental way. Please share your feedback for the same. |
|
The CI is red |
|
@electrum I am going to merge this soon, please let me know if you have any comments. I will be happy to address any more comments you might have as follow pull request just in case. Thank |
|
@Praveen2112 I'd like to review it too. Give me couple of hours please |
|
@wendigo Thanks a lot |
|
@kokosing CI is green now. |
|
@Praveen2112 go for it! |
Description
This PR utilizes the framework for injecting custom secrets provider from Airlift across various modules like connectors, group providers, resource managers etc -
Additional context and related issues
Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text: