-
Notifications
You must be signed in to change notification settings - Fork 12
Conversation
Signed-off-by: Chris Giblin <[email protected]>
Signed-off-by: Chris Giblin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @chris-giblin, I've made a first pass.
Presumably a production deployment would use HTTPS, so eventually we'll need tests (and perhaps configs?) for that. I further assume you don't want to bit this off here, which is fine, but can you open an issue for this so we don't forget?
kms-vault/src/main/java/io/strimzi/kafka/topicenc/kms/vault/VaultKms.java
Show resolved
Hide resolved
kms-vault/src/main/java/io/strimzi/kafka/topicenc/kms/vault/VaultKms.java
Outdated
Show resolved
Hide resolved
kms-vault/src/main/java/io/strimzi/kafka/topicenc/kms/vault/VaultKms.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Chris Giblin <[email protected]>
Signed-off-by: Chris Giblin <[email protected]>
Signed-off-by: Chris Giblin <[email protected]>
Signed-off-by: Chris Giblin <[email protected]>
The URL in the unit test is indeed http. That is the protocol used by Vault's dev mode which the test assumes. This should go away when testcontainers are introduced through Isssue #37 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM.
Add Vault as a KMS provider using Java ServiceLoader