feat: set or update environment variables dynamically (#1476) #1575
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 Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently we can get environment variables and set cache. But there's no feature for setting environment variables dynamically. This could be useful even when testing the server locally so to make it dynamically updated when reloaded.
Issue Number: #1476
What is the new behavior?
This PR adds feature for setting/updating environment variables with the method
set
inConfigService
. And as@nestjs/config
depends ofdotenv-expand
to resolve interpolation, I could get hint from NOT being interpolated.So after getting environment paths from module's config, simply can parse the environment variables as raw strings (I mean, like the option
expandVariables
tofalse
). And then simply just replacing interpolated variables too.This resolves #1476
Does this PR introduce a breaking change?