This repository has been archived by the owner on Apr 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
deployment.yml
32 lines (28 loc) · 1.68 KB
/
deployment.yml
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
# Choose the version of dbt that will run the project.
# Supported versions are listed in https://fivetran.com/docs/transformations/dbt/setup-guide#prerequisites.
# If the version is not specified, dbt 0.18.0 will be used.
dbtVersion: 1.0.0
jobs:
# Give each job a unique name. The name will be displayed in the Fivetran dashboard once your jobs are imported.
- name: daily
schedule: 0 12 * * * # Define when this job should run, using cron format. This example will run every day at 12:00pm (according to your warehouse timezone). For help with cron formatting, visit https://crontab.guru/.
steps:
- name: run models # Give each step in your job a name. This will enable you to track the steps in the logs.
command: dbt run # Enter the dbt command that should run in this step. This example will run all your models. For a list of available commands visit https://docs.getdbt.com/reference/model-selection-syntax/.
- name: test models
command: dbt test # This example will run all your tests.
- name: nightly
schedule: 0 0 * * * # This example will run every day at midnight.
steps:
- name: run models
command: dbt run --models my_first_model my_second_model # This example will run two specific models.
- name: weekdays
schedule: 30 7 * * 1-5 # The example will run every weekday at 7:30am.
steps:
- name: run models
command: dbt run
- name: every30minutes
schedule: '*/30 * * * *' # The example will run every 30 minutes. Note that the cron string is quoted as otherwise it will be treated as invalid alias node (see https://yaml.org/spec/1.2/spec.html#*%20alias// for details)
steps:
- name: version
command: dbt --version