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.
Motivation
Some users expressed the need for a centralized and flexible way to replace placeholders across multiple configuration files. Until now, this often required duplicating sensitive or shared values (e.g. database credentials, service endpoints, secrets) across many different configs, making maintenance error-prone and inconvenient.
To solve this, I created the Replacer module, which allows defining placeholder replacement rules in a single configuration and applying them dynamically across multiple files. This eliminates the need to manually update the same values in many places and reduces the risk of configuration inconsistencies.
#1354
Modification
ALL,FIRST, etc.)%taskName%,%nodeId%,%serviceHost%)Result
Before:
Placeholder values and secrets had to be duplicated manually across many different configuration files, making updates tedious and risky.
After:
All placeholder replacements can now be managed from a single centralized configuration, automatically applied to all matching files and targets.
Impact: