Environment variables in configuration in Spring Boot - Step-by-Step Execution

Concept Flow - Environment variables in configuration

Start Application

↓

Load application.properties

↓

Detect placeholders like ${ENV_VAR}

↓

Check OS Environment Variables

↓

Replace with value

↓

Inject values into Spring Beans

↓

Application runs with config values

Spring Boot reads configuration files, replaces placeholders with environment variable values, then injects them into the app.

Execution Sample

Spring Boot

spring.datasource.url=${DB_URL}
spring.datasource.username=${DB_USER:defaultUser}
spring.datasource.password=${DB_PASS}

This config uses environment variables DB_URL, DB_USER (with default), and DB_PASS for database connection.

Execution Table

Step	Config Line	Placeholder	Env Var Found?	Value Used	Action
1	spring.datasource.url=${DB_URL}	${DB_URL}	Yes	jdbc:mysql://localhost:3306/mydb	Replace placeholder with env var value
2	spring.datasource.username=${DB_USER:defaultUser}	${DB_USER}	No	defaultUser	Use default value as env var missing
3	spring.datasource.password=${DB_PASS}	${DB_PASS}	Yes	secretPass	Replace placeholder with env var value
4	Inject values into beans	-	-	-	Spring injects resolved values into datasource bean
5	Application starts	-	-	-	App runs with configured datasource

💡 All placeholders resolved; application configuration complete.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
DB_URL	Not set in code	jdbc:mysql://localhost:3306/mydb	jdbc:mysql://localhost:3306/mydb	jdbc:mysql://localhost:3306/mydb	jdbc:mysql://localhost:3306/mydb
DB_USER	Not set in code	Not found	defaultUser	defaultUser	defaultUser
DB_PASS	Not set in code	Not found	Not found	secretPass	secretPass

Key Moments - 3 Insights

What happens if an environment variable is missing but a default value is provided?

The default value is used instead of the missing environment variable, as shown in step 2 of the execution_table where DB_USER is missing but defaultUser is used.

What if an environment variable is missing and no default is given?

Spring Boot will fail to start or throw an error because it cannot resolve the placeholder, unlike DB_PASS which must be set or the app won't start.

How does Spring Boot inject these resolved values into the application?

After resolving placeholders, Spring injects the final values into beans like the datasource bean, as shown in step 4 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what value is used for spring.datasource.username?

A DB_USER

B null

C defaultUser

D secretPass

💡 Hint

Check step 2 in the execution_table where DB_USER is not found and defaultUser is used.

At which step does Spring Boot inject the resolved environment variable values into the application beans?

A Step 1

B Step 4

C Step 3

D Step 5

💡 Hint

Refer to the 'Action' column in step 4 of the execution_table.

If DB_PASS environment variable was missing, what would happen according to the execution flow?

A Application fails to start

B Spring uses a default password

C Placeholder remains unresolved but app runs

D Spring ignores the password

💡 Hint

See key_moments about missing env vars without defaults and step 3 in execution_table.

Concept Snapshot

Spring Boot reads config files with placeholders like ${ENV_VAR}.
It replaces placeholders with environment variable values.
If missing, it uses defaults if provided, else errors.
Resolved values are injected into beans.
This allows flexible config without code changes.

Full Transcript

In Spring Boot, configuration files can include placeholders like ${DB_URL} that refer to environment variables. When the application starts, Spring Boot loads these files and looks for such placeholders. It then checks the operating system environment variables for matching names. If found, it replaces the placeholder with the environment variable's value. If not found but a default value is provided (like ${DB_USER:defaultUser}), it uses that default. If no default is given and the variable is missing, the application will fail to start. After resolving all placeholders, Spring Boot injects these values into the relevant beans, such as the datasource bean for database connections. This process allows the application to be configured flexibly across different environments without changing code.