Use LazySecretKeysHandler for Jasypt Config #6191
Merged
Conversation
This file contains 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
zhfeng
approved these changes
Jun 17, 2024
oscerd
approved these changes
Jun 17, 2024
There was a problem hiding this comment.
Thanks so much for this @radcortez.
I left a question about some of the test changes.
...t/src/test/java/org/apache/camel/quarkus/component/jasypt/JasyptPasswordNotProvidedTest.java
Show resolved
Hide resolved
jamesnetherton
approved these changes
Jun 17, 2024
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.
This uses
LazySecretKeysHandlerto allow the JasyptSecretKeyHandlerto only initialize when a value requires the handler. This also allows for Configurable Config sources to contribute configuration to the handler.Because we don't know when the handler is going to be initialized, we create a separate instance of the Encryptor for the DevUI.