dbt_project.yml configuration - Step-by-Step Execution

Concept Flow - dbt_project.yml configuration

Start: Create dbt_project.yml

↓

Define project name

↓

Set version

↓

Configure profile name

↓

Set source-paths

↓

Set target-path

↓

Configure models settings

↓

Save and run dbt

↓

End

This flow shows how you create and configure the dbt_project.yml file step-by-step to set up your dbt project.

Execution Sample

dbt

name: 'my_dbt_project'
version: '1.0'
profile: 'default'
source-paths: ['models']
target-path: 'target'
models:
  my_dbt_project:
    +materialized: view

This config sets the project name, version, profile, source and target paths, and model materialization to view.

Execution Table

Step	Config Key	Value Set	Effect
1	name	'my_dbt_project'	Sets the project name
2	version	'1.0'	Defines project version
3	profile	'default'	Links to profile for DB connection
4	source-paths	['models']	Where dbt looks for model files
5	target-path	'target'	Where compiled files are saved
6	models.my_dbt_project.+materialized	view	Sets models to materialize as views
7	Run dbt	N/A	dbt uses this config to build models

💡 All config keys set, dbt ready to run with these settings

Variable Tracker

Config Key	Initial	Set Value	Final
name	None	'my_dbt_project'	'my_dbt_project'
version	None	'1.0'	'1.0'
profile	None	'default'	'default'
source-paths	None	['models']	['models']
target-path	None	'target'	'target'
models.my_dbt_project.+materialized	None	view	view

Key Moments - 3 Insights

Why do we set 'profile' in dbt_project.yml?

The 'profile' key tells dbt which database connection settings to use, linking to your profiles.yml file. See execution_table step 3.

What happens if 'source-paths' is set incorrectly?

dbt won't find your model files and won't build them. This is shown in execution_table step 4 where source-paths is set to ['models'].

Why do we use '+materialized: view' under models?

This sets all models in the project to be materialized as views instead of tables. See execution_table step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what value is set for 'profile' at step 3?

A 'default'

B 'my_dbt_project'

C '1.0'

D 'target'

💡 Hint

Check the 'Value Set' column in execution_table row with Step 3

At which step does the configuration specify where dbt looks for model files?

A Step 6

B Step 2

C Step 4

D Step 5

💡 Hint

Look for 'source-paths' in the Config Key column of execution_table

If you change '+materialized' from 'view' to 'table', which step in execution_table changes?

A Step 3

B Step 6

C Step 4

D Step 5

💡 Hint

Check the step where '+materialized' is set in execution_table

Concept Snapshot

dbt_project.yml configures your dbt project.
Key settings: name, version, profile (DB connection), source-paths (model files), target-path (compiled files).
Models section sets how models build (e.g., materialized as views or tables).
Save and run dbt to apply these settings.

Full Transcript

This visual execution shows how to configure the dbt_project.yml file step-by-step. First, you set the project name and version. Then, you specify the profile to connect to your database. Next, you tell dbt where to find your model files with source-paths and where to save compiled files with target-path. Finally, you configure model settings like materialization type. Each step updates the configuration variables. When all are set, dbt uses this file to build your project models correctly.