Skip to content
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.

Sign up for GitHub

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

remove description value from model notifications example #6702

Merged
merged 4 commits into from
Dec 23, 2024
Merged

remove description value from model notifications example #6702

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
38013cc
remove description value from model notifications example
mirnawong1 Dec 20, 2024
cb4e20b
Update website/docs/docs/deploy/model-notifications.md
mirnawong1 Dec 20, 2024
84c82d6
Merge branch 'current' into mirnawong1-patch-26
mirnawong1 Dec 23, 2024
ae3109e
Merge branch 'current' into mirnawong1-patch-26
mirnawong1 Dec 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions website/docs/docs/deploy/model-notifications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading