Skip to content

Commit

Permalink
remove description value from model notifications example
Browse files Browse the repository at this point in the history
this pr removes the `description` field/value from the groups.yml example. this is to make sure it isn't confused with the `description` config that dbt uses. 

pr also adds a callout clarifying that the `owner` field accepts any input (liek favorite_food).
  • Loading branch information
mirnawong1 authored Dec 20, 2024
1 parent 2edca28 commit 38013cc
Showing 1 changed file with 12 additions and 4 deletions.
16 changes: 12 additions & 4 deletions website/docs/docs/deploy/model-notifications.md
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` value 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

0 comments on commit 38013cc

Please sign in to comment.