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
{{ message }}
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.
A .env file with spaces can't be sourced unless the values are quoted, but then the quotes are preserved in the rendered output, but not preserved in the shell:
$ cat test.env
FOO="one two three"
$ source test.env
$ echo $FOO
one two three
$ cat test.conf
BAR = {{ FOO }}
$ j2 test.conf test.env
BAR = "one two three"
If I change test.env to remove the quotes, then sourcing no longer works:
$ cat test.env
FOO=one two three
$ j2 test.conf test.env
BAR = one two three
$ source test.env
Command 'two' not found, did you mean:
...
How can I create a .env with values that have spaces that is consistent between the shell and the j2 output?
The text was updated successfully, but these errors were encountered:
A
.env
file with spaces can't besource
d unless the values are quoted, but then the quotes are preserved in the rendered output, but not preserved in the shell:If I change
test.env
to remove the quotes, then sourcing no longer works:How can I create a
.env
with values that have spaces that is consistent between the shell and the j2 output?The text was updated successfully, but these errors were encountered: