Environment variables vs local variables in Bash Scripting - When to Use Which

The Big Idea

What if you could change a password once and have every script know it instantly?

The Scenario

Imagine you write a script that needs to use a username and password in many places. You type them again and again inside each part of the script or in every new script you create.

The Problem

This manual way is slow and risky. If you mistype the username or password somewhere, your script breaks. Also, if you want to change the username, you must find and update every spot manually. It's easy to forget one and cause errors.

The Solution

Using environment variables lets you store values once and share them across scripts and commands automatically. Local variables keep data inside a script or function safely. This way, you avoid repeating data and reduce mistakes.

Before vs After

✗ Before

username="user1"
password="pass1"
echo $username
# repeated in many scripts

✓ After

export USERNAME="user1"
export PASSWORD="pass1"
echo $USERNAME
# accessible in all scripts

What It Enables

You can easily share important data across scripts or keep it private inside functions, making your automation smarter and safer.

Real Life Example

When deploying a website, you set database login info as environment variables once. All deployment scripts use these variables without rewriting sensitive info everywhere.

Key Takeaways

Local variables store data inside a script or function only.

Environment variables share data across scripts and processes.

Using them reduces errors and saves time updating repeated info.

Practice

1. What is the main difference between an environment variable and a local variable in a Bash script?

easy

A. Local variables are available to child processes, environment variables are not.

B. Environment variables are available to child processes, local variables are not.

C. Environment variables can only be numbers, local variables can be strings.

D. Local variables are global, environment variables are only inside functions.

Solution

1. Step 1: Understand environment variables

   Environment variables are set with export and are inherited by child processes.

2. Step 2: Understand local variables

   Local variables exist only in the current shell or function and are not passed to child processes.

3. Final Answer:

   Environment variables are available to child processes, local variables are not. -> Option B

4. Quick Check:

   Environment = exported, local = not exported [OK]

Hint: Remember: export makes variables visible to child processes [OK]

Common Mistakes:

• Thinking local variables are inherited by child processes
• Confusing export with local keyword
• Assuming environment variables are only inside functions

2. Which of the following is the correct way to create a local variable inside a Bash function?

easy

A. VAR=value

B. export VAR=value

C. local VAR=value

D. setlocal VAR=value

Solution

1. Step 1: Identify local variable syntax in Bash functions

   Inside a function, the keyword local declares a variable limited to that function.

2. Step 2: Compare options

   export makes variables environment variables, setlocal is not a Bash command, and VAR=value without local is global or inherited.

3. Final Answer:

   local VAR=value -> Option C

4. Quick Check:

   Use local inside functions for local variables [OK]

Hint: Use 'local' keyword inside functions for local variables [OK]

Common Mistakes:

• Using export instead of local inside functions
• Assuming VAR=value inside function is local
• Using non-existent commands like setlocal

3. What will be the output of this script?

VAR=hello
function test_func() {
  local VAR=world
  echo $VAR
}
test_func
echo $VAR

medium

A. world
hello

B. hello
hello

C. world
world

D. hello
world

Solution

1. Step 1: Analyze variable inside function

   The function declares a local variable VAR with value 'world', so echo $VAR inside prints 'world'.

2. Step 2: Analyze variable outside function

   The global VAR remains 'hello', so echo $VAR after function call prints 'hello'.

3. Final Answer:

   world hello -> Option A

4. Quick Check:

   Local inside function, global outside [OK]

Hint: Local variables override global only inside functions [OK]

Common Mistakes:

• Assuming local variable changes global variable
• Confusing output order
• Ignoring local keyword effect

4. Identify the error in this script snippet:

export VAR=hello
function test() {
  VAR=world
  local VAR
  echo $VAR
}
test
echo $VAR

medium

A. local must be declared before assigning VAR inside function

B. export cannot be used outside functions

C. echo $VAR inside function will print empty

D. Function syntax is incorrect

Solution

1. Step 1: Understand local variable declaration order

   In Bash, local VAR must appear before assigning a value to VAR inside the function to make it local.

2. Step 2: Analyze the script behavior

   Here, VAR=world assigns to global VAR before local VAR is declared, so local VAR is empty and echo $VAR prints empty.

3. Final Answer:

   local must be declared before assigning VAR inside function -> Option A

4. Quick Check:

   Declare local before assignment inside functions [OK]

Hint: Declare local variables before assigning values inside functions [OK]

Common Mistakes:

• Assigning before declaring local causes unexpected behavior
• Thinking export is invalid outside functions
• Assuming function syntax is wrong

5. You want to write a Bash script that sets a variable PATH_VAR inside a function and have it available outside the function and in any child processes. Which is the correct approach?

hard

A. Inside the function, use export PATH_VAR=value after declaring local PATH_VAR.

B. Declare local PATH_VAR=value inside the function and then export PATH_VAR outside the function.

C. Use local PATH_VAR=value inside the function and do nothing else.

D. Assign PATH_VAR=value inside the function and then export PATH_VAR inside the function without local.

Solution

1. Step 1: Understand local vs exported variables

   Declaring a variable as local limits it to the function scope, so it won't be available outside or to child processes.

2. Step 2: Correct way to export variable from function

   Assign the variable without local inside the function, then use export PATH_VAR inside the function to make it environment variable accessible outside and to child processes.

3. Final Answer:

   Assign PATH_VAR=value inside the function and then export PATH_VAR inside the function without local. -> Option D

4. Quick Check:

   Export without local to share variable outside function [OK]

Hint: Don't use local if you want variable exported outside function [OK]

Common Mistakes:

• Using local and export together inside function
• Exporting variable only outside function after local declaration
• Assuming local variables can be exported