Need a way to specify and pass env variables to the experiment run

[shcheklein]

In enterprise environment there are usually a bunch of env vars that we need to set to access things like proxy, custom SSL certs, etc, etc. It can be set usually via bashrc or exists as part of the environment.

As far as I understand VS Code doesn't pick up any variables at all - that breaks the run experiment functionality.

• Is it true, need to confirm
• Since there is no easy way to grab those - let's provide some mechanics to workaround. (e.g. read .env file, or have a config where people can put those)

[mattseddon]

I think the functionality should be added to DVC through the config. That way users could add a section to their local config and we don't have to add another concept/set of rules/docs for this.

Edit: I can still pick this up if it is a priority.