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: 'central_data_team_partner_eng_inc'
version: '1.5.0'
require-dbt-version: '>=1.6.0'
config-version: 2
dbt-cloud:
  project-id: "64586"

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

# These configurations specify where dbt should look for different types of files.
# The `models-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: ["analysis"]
test-paths: ["tests"]
seed-paths: ["data"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]
clean-targets:         # directories to be removed by `dbt clean`
  - "target"
  - "dbt_packages"

on-run-start:
  - '{{create_udfs()}}' # comment / uncomment this line to build UDFs called in the create_udfs macro

on-run-end:
  - "{{ grant_all_on_schemas(schemas, 'transformer') }}"

vars:
  start_date: '1999-01-01'
  test: 'false' # to trigger runs for unit testing - override in a CLI param in testing job
  fct_order_items: 'mock_source__fct_order_items' # this is a map for unit testing
  dbt_metrics_calendar_model: all_days

# Configuring models
# Full documentation: https://docs.getdbt.com/docs/configuring-models
flags:
  require_generic_test_arguments_property: true
  
models:
  +grants:
    select: ['transformer']

  central_data_team_partner_eng_inc:
    staging:
      +materialized: view

    marts:
      tpch_marts:
        +materialized: table