-
Notifications
You must be signed in to change notification settings - Fork 960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update model-notifications #6556
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -33,7 +33,9 @@ Create configuration YAML files in your project for dbt to send notifications ab | |||
|
|||
## Configure groups | |||
|
|||
Add your group configuration in either the `dbt_project.yml` or `groups.yml` file. For example: | |||
Define your groups in any .yml file in your [models directory](/reference/project-configs/model-paths). For example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is wrong and is the main thing I wanted to do in the PR
# Email is required to receive model-level notifications, additional properties are also allowed. | ||
name: "Finance Team" | ||
email: [email protected] | ||
slack: finance-data | ||
favorite_food: donuts | ||
|
||
- name: marketing | ||
description: "Models related to the marketing department" | ||
owner: | ||
name: "Marketing Team" | ||
email: [email protected] | ||
slack: marketing-data | ||
favorite_food: jaffles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for clarity and is optional, but reduces the likelihood people misbelieve that Slack notifs are supported
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good callout! i assumed slack was supported when reading
</File> | ||
|
||
## Attach groups to models | ||
|
||
Attach groups to models as you would any other config, in either the `dbt_project.yml` or `<whatever>.yml` files. For example: | ||
|
||
Set up your model configuration in either the `dbt_project.yml` or `groups.yml` file; doing this automatically sets up notifications for tests, too. For example: | ||
<File name='models/marts.yml'> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rest of this is purely additive and you can rework as you see fit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for adding the files tag! 🙏
</File> | ||
|
||
By assigning groups in the `dbt_project.yml` file, you can capture all models in a subdirectory at once. In the below example, all notifications related to staging models will go to the data engineering group, whereas models in `marts/sales` will be routed to the finance team. | ||
|
||
<File name='dbt_project.yml'> | ||
|
||
```yml | ||
config-version: 2 | ||
name: "jaffle_shop" | ||
|
||
[...] | ||
|
||
models: | ||
jaffle_shop: | ||
staging: | ||
+group: data_engineering | ||
marts: | ||
sales: | ||
+group: finance | ||
campaigns: | ||
+group: marketing | ||
|
||
``` | ||
|
||
</File> | ||
Attaching a group to a model also encompasses its tests, so you will also receive notifications for a model's test failures. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As is this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great to me and thanks for adjusting this @joellabes , made some small tweaks for clarity and merging for you!
Check your created Crawler Check your created index on your Algolia Application |
What are you changing in this pull request and why?
dbt_project.yml
.🚀 Deployment available! Here are the direct links to the updated files: