
18 May
2018
18 May
'18
6 p.m.
On 05/18/2018 08:44 AM, Quentin Schulz wrote:
While the `env export` can take as parameters variables to be exported, `env import` does not have such a mechanism of variable selection.
Let's add a `-w` option that asks `env import` to look for the `whitelisted_vars` env variable for a space-separated list of variables that are whitelisted.
Would it be better for the -w option to accept a variable name rather than hard-coding it as whitelisted_vars? That way, people could import/export different sets of variables at different times, and also could choose a more use-case-specific variable name than whitelisted_vars in order to describe why those variables are "whitelisted".