profiles.yml

# Copyright 2023 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# 1) Fill in your GCP project name and desired dataset name.
# 2) These settings are meant for "oauth via gcloud" authentication. You need to follow these
#    instructions:
#    https://docs.getdbt.com/reference/warehouse-setups/bigquery-setup#local-oauth-gcloud-setup
#    You can also check other options for BigQuery authentication in
#    https://docs.getdbt.com/reference/warehouse-setups/bigquery-setup#authentication-methods.

fhir_dbt_analytics:
  target: dev
  outputs:
    dev:
      # Name of your GCP project in which the dataset will be created and BigQuery jobs run.
      # See here for creating a new GCP project:
      # https://cloud.google.com/resource-manager/docs/creating-managing-projects
      project: <TODO: Fill in details in profiles.yml>

      # Name of the dataset that dbt creates and writes to.
      # Recommended: dbt_<username>. See here for more details:
      # https://docs.getdbt.com/docs/get-started/connection-profiles#understanding-target-schemas
      dataset: "dbt_{{ env_var('USER', 'unknown_user') }}"

      # See https://docs.getdbt.com/docs/get-started/connection-profiles#understanding-threads.
      threads: 4

      # Location of your dbt outputs must be the same as the location of your FHIR sources.
      # See https://docs.getdbt.com/reference/warehouse-setups/bigquery-setup#dataset-locations.
      location: <TODO>

      job_execution_timeout_seconds: 300
      job_retries: 1
      method: oauth
      priority: interactive
      type: bigquery