Closed ajcrites closed 4 years ago
If you have a .env file like this:
.env
NAME="Value"
running envsub --env-file .env results in a substitution of ${NAME} for "Value".
envsub --env-file .env
${NAME}
"Value"
However, running NAME="Value" envsub results in Value (not wrapped in quotes).
NAME="Value" envsub
Value
I think that quotes should be ignored when setting values from a key=value file as you might expect when sourcing the file in a shell environment.
Given the increase in downloads on this module I am planning to be more active - will investigate this issue and get back to you
This is fixed in 4.0.2 - closing
If you have a
.env
file like this:running
envsub --env-file .env
results in a substitution of${NAME}
for"Value"
.However, running
NAME="Value" envsub
results inValue
(not wrapped in quotes).I think that quotes should be ignored when setting values from a key=value file as you might expect when sourcing the file in a shell environment.