feat: Add support for using env vars in config #10
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.
PR(Pull Request) Overview
This change allows users to add tags to the configuration file which can be replaced via environment variables.
This can be useful in cases were access tokens should be injected into the config, but should not be directly
stored in the config file.
Changes
Description of Changes
This change invokes a search and replace routine before the loaded config is unmarshaled by the yaml parser.
The function searches for all entries matching the regex (
${...}
) and tries to load an environment variableof the same name. If nothing is found nothing will be replaced.
Testing Method
I added a small unit test to
config_test.go
Additional Information
I was considering using the
text/template
package instead, but decided otherwise as I wanted to keep thefunctionality at a minimum and not add additional support for more templating.