dbt_tests_source:
  outputs:
    prod_source:
      type: mysql5
      host: [HOST]
      password: [PASS]
      port: 3306
      threads: 4
      user: [USER]
  target: prod_source

elementary:
  outputs:
    prod_data_warehouse:
      type: "redshift"
      host: [HOST]
      port: 5439
      user: [USER]
      password: [PASS]
      dbname: "production"
      schema: "data_quality_dbt_source_aspireapp_elementary"
      threads: 10
  target: prod_data_warehouse

config-version: 2

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

# 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"]

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 views. These settings can be overridden in the individual model
# files using the `{{ config(...) }}` macro.
models:
  elementary:
    ## elementary models will be created in the schema '<your_schema>_elementary'
    # +schema: "elementary"
    ## To disable elementary for dev, uncomment this:
    # enabled: "{{ target.name in ['prod','analytics'] }}"

flags:
  require_explicit_package_overrides_for_builtin_materializations: True
  require_model_names_without_spaces: False
  source_freshness_run_project_hooks: False