Vault-lookup support for properties files #1575
Open
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.
Purpose
Use vault-lookup to decrypt a value in a properties file
Goals
Read the encrypted password from the
conf/security/cipher-tool.properties
or any other java '.properties' file.Approach
It's basically a copy of the FilePropertiesRepository.
In the call
wso2:vault-lookup('<alias>', '<type>', '<isEncripted>')
, the '' enum was expanded to contain 'property'. Thealias
, which was also used as file path, is now splitted at ':'. The last element is used as property name, the others are assumed to be part of the filename.Usage:
wso2:vault-lookup('conf/security/cipher-text.properties:SomeExamplePassword', 'PROPERTY', 'true')
User stories
Release note
Documentation
Training
Certification
Marketing
Automation tests
Security checks
Samples
Related PRs
Migrations (if applicable)
Test environment
Learning