Please check if your PR fulfills the following requirements:
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (npm run build:check or yarn build:check) was run locally and any changes were pushed
[x] Lint (npm run lint or yarn lint) has passed locally and any fixes were made for failures
Pull request type
Please check the type of change your PR introduces:
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the new behavior?
In a YAML config file, you can replace variables. Currently only environment variables are supported but anywhere in the config file you can have:
${env:SOME_VAR_NAME}
And this will use process.env.SOME_VAR_NAME. If the value of that is undefined, then the text is not replaced. If the type is unrecognized (the env part in the sample) then the text is not replaced.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build:checkoryarn build:check) was run locally and any changes were pushednpm run lintoryarn lint) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the new behavior?
In a YAML config file, you can replace variables. Currently only environment variables are supported but anywhere in the config file you can have:
${env:SOME_VAR_NAME}And this will use
process.env.SOME_VAR_NAME. If the value of that isundefined, then the text is not replaced. If the type is unrecognized (theenvpart in the sample) then the text is not replaced.Does this introduce a breaking change?