Shell – In bash, how can I export/set a global variable from a read funtion inside a script, for use in a second script and a config file later on

I assume you can run the script with: ./script1.sh (which start the script in a shell) instead of . script1.sh (which will source them in your current shell) ?

If so:

#!/bin/bash

./script1.sh   &&
{ ssh user@remote "cd /path/to/  && script2.sh" ; }  &&
./script3.sh   &&
./script4.sh

&& ensure that the following instructions is executed ONLY if the previous returned "0" (="ok") (so make sure your script does return the proper "0" if OK, and something else (a small positive integer, such as "1") if NOT OK).

(Note that you can have && at the end of a line, as I did here, and the following thing on the next line, without the need to \ the newline in-between. "&&" at the end of the line tells bash that the line can be continued on the following line. [thank to @Dennis for correcting me: I thought it also worked to not put a '\newline' when "&&" was on the next line, which is more readable... but doesn't work. If you want "&&" on the next line, you need to backslash the previous newline])

To summarize, you want to retrieve a value out of script1.sh without running all the commands in script1.sh. I will assume that script1.sh is not under your control, possibly because it is vendor-provided, or managed by an obstinate colleague, or similar such issue, which makes it so that script1.sh has to be used as is.

I will present two approaches. The first is good for getting specific variables out of script1.sh, one at time:

var=$(awk -F'"' '/^variable=/ {print $2}' script1.sh )
echo $var

This uses awk to read (not execute, just read) script1.sh. awk looks for the line that begins with variable= and then writes what appears after the double-quote mark on that line. The output from awk is capture into variable var.

In more detail:

• The statement is of the form var=$(...). This means that whatever is in the parentheses is run as a bash command and its standard output is assigned to the variable var.

• Inside the parentheses, we have the awk command: awk -F'"' '/^variable=/ {print $2}' script1.sh. Let us consider it in parts.

• awk breaks lines (records) into fields. -F'"' tells awk to use double-quote as a field separator.

• /^variable=/ tells awk to restrict operation to lines that begin with variable=. Thus, all the miscellaneous commands in script1.sh will be ignored.

• {print $2} tells awk to print the second field. This means whatever is between the first and second occurence of a double-quote character.

• The last argument to awk tells it what file to read: script1.sh.

The above approach is good for handling one variable at a time and allows you to rename the variable if you like.

How to handle many variables

If you want to source all the variables assigned in script1.sh, consider:

source <(grep -E '^\w+=' script1.sh)

This uses grep to extract all lines from script1.sh that look like variable assignments. These lines are then run in the current shell, assigning the variables.

If you use this approach first check to make sure that you want all the variables and that there aren't any that will interfere with what you are doing. If there are such, we can exclude them with a second grep command.

Considering the pieces in turn:

• source file tells the shell to execute the file in the current shell.

• <(...) is called process substitution. It allows us to use the output of a command in place of a file name.

• The command grep -E '^\w+=' script1.sh extracts all lines that seem like variable assignments. If you run this command by itself on the command line, you should see something like:

  variable="Hello"
  var2="Value2"
  

  and so on. You should do this first and inspect the output to make sure that these are the lines that you want to execute.