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: "emd"
version: "1.0.0"
config-version: 2

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

# These configurations specify where dbt should look for different types of files.
# The `source-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!
source-paths: ["models"]
analysis-paths: ["analysis"]
test-paths: ["tests"]
data-paths: ["data"]
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_modules"

vars:
  ### Date default variables ###
  date_range_start: "None"
  date_range_end: "2022-12-16"

# Grant acess
  # bq data control: https://cloud.google.com/bigquery/docs/reference/standard-sql/data-control-language
  # dbt grant statements use https://discourse.getdbt.com/t/the-exact-grant-statements-we-use-in-a-dbt-project/430

# 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:
  +post-hook: 'GRANT `roles/bigquery.dataViewer` ON TABLE {{ this }} TO "specialGroup:allUsers"'
  +persist_docs:
    relation: true
    columns: true
  emd:
    adm_central_atendimento_1746:
      +materialized: table
      +schema: adm_central_atendimento_1746
    adm_cor_comando:
      +materialized: table
      +schema: adm_cor_comando
    dados_mestres:
      +materialized: table
      +schema: dados_mestres
    educacao_basica:
      +materialized: table
      +schema: educacao_basica
    meio_ambiente_clima:
      +materialized: table
      +schema: meio_ambiente_clima
    clima_pluviometro:
      +materialized: table
      +schema: clima_pluviometro
    clima_fluviometro:
      +materialized: table
      +schema: clima_fluviometro
    clima_estacao_meteorologica:
      +materialized: table
      +schema: clima_estacao_meteorologica
    planejamento_gestao_acordo_resultados:
      +materialized: table
      +schema: planejamento_gestao_acordo_resultados
    transporte_rodoviario_municipal:
      +materialized: table
      +schema: transporte_rodoviario_municipal
    turismo_fluxo_visitantes:
      +materialized: table
      +schema: turismo_fluxo_visitantes