Native .env file support?

[mattwaler]

I'm using .env files to do all of my secret hiding. It kinda stinks to have to translate the values to JSON in the settings folder. Is it feasible/possible to be able to access .env file values at the root of the folder to be accessible by the extension? Maybe via {{$dotenv PORT}} for a file named .env and {{$dotenvLocal PORT}} for a .env.local file?

[Huachao]

@mattwaler nice suggestion, I will implement it and update in this thread later

[Huachao]

@mattwaler @Ruegen @yfwz100 @devalnor I have supported the {{$dotenv variableName}} syntax, and you just need to put the .env file in the same folder of your .http file. However, .env.local file is not supported currently.

[mattwaler]

Awesome! Thank you so much for this amazing extension.

[Huachao]

@mattwaler @Ruegen @yfwz100 @devalnor you can try the latest version 0.23.0 to verify it.

[yfwz100]

It works, Thanks!

[tomdavidson]

Is the use case of {{$dotenv variableName}} in an environment variable value supported?

[mattwaler]

@tomdavidson Yes, when the .env file and .http file are in the same directory this works as intended.

[tomdavidson]

@mattwaler thanks, ill open up a new issue then - #489

[rufreakde]

@Huachao does this syntax also work in the workspace config?

  "rest-client.certificates": {
    "<domain>": {
      "pfx": "test/some/path/dev/cert", //change the p12 cert paths for different landscapes
      "passphrase": "{{$dotenv pass}}" //p12 passphrase

This seems not to work any pointers here?

Issue:
#1135

[shaunakv1]

@Huachao can we specify the location of .env file? or walk up to the root of current vscode project? My .env file usually lives in the root of code, and .http files are in a test directory

[nazarEnzo]

.env does not have to be in the same folder anymore. I used existing .env in the root of the project while making requests from subfolders and it works perfectly fine 👍