stellar-dbt-public/dbt_project.yml at master · stellar/stellar-dbt-public · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
name: "stellar_dbt_public" # the name of a dbt project
version: "1.0.0" # version of your project
config-version: 2

profile: "stellar_dbt_public" # the profile dbt uses to connect to your data platform

# 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"] # directories where models and sources are located
analysis-paths: ["analyses"] # directories where analyses are located
test-paths: ["tests"] # directories where singular or generic test files are located
seed-paths: ["seeds"] # directories where seed files are located
macro-paths: ["macros"] # directories where macros are located
snapshot-paths: ["snapshots"] # directories where snapshots are located

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

flags:
  require_explicit_package_overrides_for_builtin_materializations: false

vars:
  dbt_project_evaluator:
    documentation_coverage_target: 50
    test_coverage_target: 50
    exclude_packages: ["elementary"]

  airflow_start_timestamp: "{{ env_var('AIRFLOW_START_TIMESTAMP', '2000-01-01') }}"
  # overridden in specific Airflow tasks
  is_recency_airflow_task: "false"
  is_singular_airflow_task: "{{ env_var('IS_SINGULAR_AIRFLOW_TASK', 'false') }}"
  snapshot_start_date: "{{ env_var('SNAPSHOT_START_DATE', '2000-01-01') }}"
  snapshot_end_date: "{{ env_var('SNAPSHOT_END_DATE', '2000-01-02') }}"
  snapshot_full_refresh: "{{ env_var('SNAPSHOT_FULL_REFRESH', 'false') }}"
  execution_date: "{{ env_var('EXECUTION_DATE', '2000-01-01') }}"
  batch_start_date: "{{ env_var('BATCH_START_DATE', '2000-01-01') }}"
  batch_end_date: "{{ env_var('BATCH_END_DATE', '2000-01-02') }}"

# Configuring models
# Full documentation: https://docs.getdbt.com/docs/configuring-models
models:
  stellar_dbt_public:
    staging:
      +materialized: view # how the staging models will be materialized
    intermediate:
      +materialized: table # how the intermediate models will be materialized
    marts:
      +materialized: table # how the mart models will be materialized
    snapshots:
      +materialized: incremental_snapshot

  elementary:
    +schema: elementary
    +docs:
      show: false

  dbt_project_evaluator:
    +dataset: dbt_project_evaluator
    +enabled: "{{ target.name != 'prod' }}"
    marts:
      dag:
        fct_model_fanout:
          +enabled: false
      structure:
        fct_source_directories:
          +enabled: false
        fct_model_naming_conventions:
          +enabled: false
        fct_model_directories:
          +enabled: false
      tests:
        fct_missing_primary_key_tests:
          +enabled: false
        fct_sources_without_freshness:
          +enabled: false
      documentation:
        fct_undocumented_sources:
          +enabled: false

seeds:
  stellar_dbt_public:
    dbt_project_evaluator_config:
      +dataset: dbt_project_evaluator
  dbt_project_evaluator:
    dbt_project_evaluator_exceptions:
      +enabled: false

tests:
  dbt_project_evaluator:
    +severity: "{{ env_var('DBT_PROJECT_EVALUATOR_SEVERITY', 'error') }}"