Variables are being set as shell variables, not environment variables

Question

Variables are being set as shell variables, not environment variables

Closed this issue 7 years ago · 3 comments

waldoj commented 7 years ago

As a result, they don't exist within child processes, which is to say that they are useless. Fix this.

Answer 1 · 2018-01-12T03:45:17.000Z

The solution is to export all of them.

Answer 2 · 2018-01-13T00:38:23.000Z

These are all working fine, except for filename:

filename=$'"../video/20180111.mp4"\ndate="20180111"\ndate_hyphens="2018-01-11"\ns3_url="https://s3.amazon.com/house/floor/20180111.mp4"\nchamber="house"'

I'm not sure what's going on here.

Answer 3 · 2018-01-16T00:53:14.000Z

Huh. So, yeah, adding export to the start of this is the source of the problem:

export eval "$(jq -r '. | to_entries | .[] | .key + "=\"" + .value + "\""' < metadata.json)"

Without that, they work fine as shell variables.