You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently bens exports all the environmental variables from the yaml file when calling the "environmental" command. If you use the same yaml files for different projects that all require different overlapping subsets of the variables this can make cleaning the environment files you don't need out of the environment difficult. This issues can be worked around with some shell scripting:
eval $(bens environment | grep -E '(var1)|(var3)'
but a built in option could be cleaner:
eval $(bens environement -e var1 -e var2
The text was updated successfully, but these errors were encountered:
Currently bens exports all the environmental variables from the yaml file when calling the "environmental" command. If you use the same yaml files for different projects that all require different overlapping subsets of the variables this can make cleaning the environment files you don't need out of the environment difficult. This issues can be worked around with some shell scripting:
but a built in option could be cleaner:
The text was updated successfully, but these errors were encountered: