I'm using a
echo -e "This is my $KEY and my profile is $PROFILE"
This is my Ru2cXJbgWQ0wdtKBGbS5/nVQvGo and my profile is foobar
-bash-4.1$ echo -e "This is my $KEY"
This is my
-bash-4.1$ env | grep KEY
$ env | grep KEY
$ env | grep DEFAULT_PROFILE
To complement Anthony Geoghegan's helpful answer:
In short: the fact that
env | grep KEY returns
KEY=Ru2cXJbgWQ0wdtKBGbS5/nVQvGo does NOT necessarily mean that an environment variable named
It is conceivable that the
grep matches you're getting are matches of other environment variables' values or even the last line of multi-line variable name. Thanks, chepner.
While environment variable and values are typically single-line, they don't have to be. An example is Bash's own ability to export functions, whose typically multi-line definitions are exported as the values of specially named environment variables.
To verify that a given (Bash) shell variable is indeed based on an environment variable, use:
declare -p KEY # example with variable name 'KEY'
KEY is indeed an environment variable, you'll see (using your example):
declare -x KEY="Ru2cXJbgWQ0wdtKBGbS5/nVQvGo"
-x, which indicates an exported variable, which is synonymous with being an environment variable.
KEY is a shell variable that isn't also an environment variable, the
-x will be missing.
KEY is neither a shell variable nor an environment variable, you'll see an error message.
anubhava, in a comment on the question, demonstrates a shell-independent way to test if an environment variable is defined:
printenv KEY # prints value of env. var. 'KEY'
An exit code of
0 tells you that the variable exists (even if it is has no value).
printenv is an external utility that is not POSIX-compliant; it does, however, come with both Linux and BSD/OSX.