-
Notifications
You must be signed in to change notification settings - Fork 978
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
remove description value from model notifications example (#6702)
- Loading branch information
Showing
1 changed file
with
12 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,21 +38,29 @@ groups: | |
- name: finance | ||
owner: | ||
# Email is required to receive model-level notifications, additional properties are also allowed. | ||
name: "Finance Team" | ||
description: "Models related to the finance department" | ||
name: "Finance team" | ||
email: [email protected] | ||
favorite_food: donuts | ||
|
||
- name: marketing | ||
owner: | ||
name: "Marketing Team" | ||
description: "Models related to the marketing department" | ||
name: "Marketing team" | ||
email: [email protected] | ||
favorite_food: jaffles | ||
|
||
- name: docs | ||
owner: | ||
name: "Documentation team" | ||
email: [email protected] | ||
favorite_food: pizza | ||
``` | ||
</File> | ||
:::tip | ||
The `owner` key is flexible and accepts arbitrary inputs in addition to the required `email` field. For example, you could include a custom field like `favorite_food` to add context about the team. | ||
::: | ||
|
||
## 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: | ||
|