-
Notifications
You must be signed in to change notification settings - Fork 819
add support for multiple test env files #3846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: jfoshee <480334+jfoshee@users.noreply.github.com>
Co-authored-by: jfoshee <480334+jfoshee@users.noreply.github.com>
... string test Co-authored-by: jfoshee <480334+jfoshee@users.noreply.github.com>
...7-daf15cc62e6d Add support for multiple test environment files via go.testEnvFiles setting
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
It's also possible to update go.testEnvFile such that it could accept both a string or an array of strings.
This PR implements support for loading multiple environment files during test execution
New Setting: go.testEnvFiles
Added go.testEnvFiles setting that accepts an array of environment file paths
Allows loading multiple .env files in a specific order for test execution
Later files in the array override variables from earlier files
Backward Compatibility
Existing go.testEnvFile setting continues to work as before
Marked go.testEnvFile as deprecated with appropriate VS Code deprecation messaging
When both settings are used together, go.testEnvFile is processed after all files in go.testEnvFiles
Fixes #2473