Configuration paths exist in your dbt_project.yml file which do not apply to any resources. There are 1 unused configuration paths:- models.dbt_project.example

Help
1

The problem I’m having

The problem I’m having is after the profiles.yml All checks passed! (the connection successful)
when i run dbt get this message
Configuration paths exist in your dbt_project.yml file which do not apply to any resources. There are 1 unused configuration paths:- models.dbt_project.example

The context of why I’m trying to do this

adapter dbt-synapse
dbt version: 1.4.1
python version: 3.9.6
python path: c:\dbt-project\python.exe
os info: Windows-10-10.0.19042-SP0
Using profiles.yml file at C:\Users\user1.dbt\profiles.yml
Using dbt_project.yml file at C:\dbt-Project\Scripts\dbt_project.yml

also here is the profiles.yml code
"
dbt_project:
target: dev
outputs:
dev:
type: synapse #synapse #type: Azuresynapse
driver: ‘ODBC Driver 17 for SQL Server’ # (The ODBC Driver installed on your system)
server: ######## # (Dedicated SQL endpoint of your workspace here)
database: ##########
port: 1433
schema: dev_dbt_dbo
user: ##########
password: #######
"

What I’ve already tried

Some example code or error messages

Models\Example

my_first_dbt_model.sql
"{{ config(materialized='table') }}

with source_data as (

    select 1 as id
    union all
    select null as id

)

dbt_project.yml
"
 Name your project! Project names should contain only lowercase characters
# and underscores. A good package name should reflect your organization's
# name or the intended use of these models
name: 'dbt_project'
version: '1.0.0'
config-version: 2

# This setting configures which "profile" dbt uses for this project.
profile: 'dbt_project'

# These configurations specify where dbt should look for different types of files.
# The `model-paths` config, for example, states that models in this project can be
# found in the "models/" directory. You probably won't need to change these!
model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]

target-path: "target"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by `dbt clean`
  - "target"
  - "dbt_packages"


# Configuring models
# Full documentation: https://docs.getdbt.com/docs/configuring-models

# In this example config, we tell dbt to build all models in the example/ directory
# as tables. These settings can be overridden in the individual model files
# using the `{{ config(...) }}` macro.
models:
  dbt_project:
    # Config indicated by + and applies to all files under models/example/
    example:
      +materialized: view
"
my_second_dbt_model.sql
"select *
from {{ ref('my_first_dbt_model') }}
where id = 1"

select *
from source_data

/*
    Uncomment the line below to remove records with null `id` values
*/

-- where id is not null
2

Looks like the issue is in this area

–this is for dbt-synapse
–I used the default one… there a different setup for dbt-synapse?

–#and underscores. A good package name should reflect your organization’s
–#name or the intended use of these models
name: ‘dbt_project’
version: ‘1.0.0’
config-version: 2

–#This setting configures which “profile” dbt uses for this project.
profile: ‘dbt_project’

–#These configurations specify where dbt should look for different types of files.
–#The model-paths config, for example, states that models in this project can be
–#found in the “models/” directory. You probably won’t need to change these!
model-paths: [“models”]
analysis-paths: [“analyses”]
test-paths: [“tests”]
seed-paths: [“seeds”]
macro-paths: [“macros”]
snapshot-paths: [“snapshots”]

target-path: “target” # directory which will store compiled SQL files
clean-targets: # directories to be removed by dbt clean

  • “target”
  • “dbt_packages”

–# Configuring models
–#Full documentation: Model configurations | dbt Developer Hub

–# In this example config, we tell dbt to build all models in the example/ directory
–#as tables. These settings can be overridden in the individual model files
–# using the {{ config(...) }} macro.
models:
dbt_project:
–# Config indicated by + and applies to all files under models/example/
example:
+materialized: view