Can anyone else confirm that this plugin is pulling environment variables system wide? #3647
Replies: 2 comments 3 replies
-
|
It should be inheriting environment variables from the environment (from VSCode) plus the relevant settings for the plugin. If you're using bash, does running |
Beta Was this translation helpful? Give feedback.
-
|
No when i run env or printenv i get less/different variables. Some environment variables like DB_USER are coming from old projects I havent touched in 2 years. I am trying to figure out why. |
Beta Was this translation helpful? Give feedback.
-
|
Does your user or folder/workspace settings file contain |
Beta Was this translation helpful? Give feedback.
-
|
I checked to ensure there were no references to any keyword |
Beta Was this translation helpful? Give feedback.
-
|
I found the problem: I have a ~/.env with old credentials in it. After upgrading all of my go tools/libraries: At first I thought it was a problem with I exited and restarted VS Code and the environment variables disappeared, which makes me think the environment variables were being injected by the Go VS Code plugin. I have a lot of other plugins installed so its hard to determine. Here is a list just for reference: |
Beta Was this translation helpful? Give feedback.
-
main_test.go
Can someone who has worked on multiple projects with different environment variables on the same computer try this test case.
When i do this I get environment variables that only exist on an archived project from a hard drive I only backup code to.
I cannot figure out why this is happening.
Any help with clearing cache / debugging would be appreciated.
I tried a system wide ripgrep searching for env var keywords. Found nothing in my code folder, only in archived code on a different hard drive.
Beta Was this translation helpful? Give feedback.
All reactions