Feat: Support env variable substitution in topology configuration files #532
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
ludovic-boutros
changed the title
sverrehu
reviewed
Sep 13, 2023
src/main/java/com/purbon/kafka/topology/serdes/SystemPropertySubstitutor.java
Outdated
Show resolved
Hide resolved
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR introduce the support of system property substitution in the topology configuration files.
What is the new behavior (if this is a feature change)?
Variable like
${environment}can be used in topology files in order to simplify the usage of split topologies (per environment and project for instance).Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
Other information:
A small fix of function naming mixed up is present in a specific commit.
If needed I can push this fix in a separate PR.
Fix #533