You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configuration.rst
+10-16Lines changed: 10 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -392,12 +392,6 @@ dbt Cloud configuration
392
392
* - project_name
393
393
- string
394
394
- Name of the project to be created in dbt Cloud
395
-
* - schedule_interval
396
-
- string
397
-
- The cron expression with which the example job will be run
398
-
* - default_gcp_project
399
-
- string
400
-
- GCP project that will be used by default if a new environment is created in dbt Cloud
401
395
* - environments
402
396
- Array
403
397
- Details of the environments to be created in dbt Cloud
@@ -414,31 +408,31 @@ Configuration of the environments:
414
408
* - name
415
409
- string
416
410
- Name of the environment that will be created in dbt Cloud
417
-
* - dataset
411
+
* - type
418
412
- string
419
-
- Target dataset for this environment
413
+
- In dbt Cloud, there are two types of environments: deployment and development. Deployment environments determine the settings used when jobs created within that environment are executed. Development environments determine the settings used in the dbt Cloud IDE for that particular dbt Cloud Project. Each dbt Cloud project can only have a single development environment but can have any number of deployment environments.
420
414
* - dbt_version
421
415
- string
422
416
- The dbt version used in this environment
423
-
* - bq_config_dir
417
+
* - schedule_interval
418
+
- string
419
+
- The cron expression with which the example job will be run. This setting is only needed for the deployment environment.
420
+
* - config_dir
424
421
- string
425
-
- The name of the dp env directory where the bigquery configuration for the environment is located. The name of the project in GCP will be read from it.
422
+
- The name of the dp env directory where the bigquery configuration for the environment is located. The name of the project in GCP and target dataset will be read from it.
426
423
427
424
Example ``dbtcloud.yml`` file might look like this:
0 commit comments