From 38013cc3dc25e592651d84634e54b5a3b2bbef3c Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 20 Dec 2024 16:59:58 +0000 Subject: [PATCH] remove description value from model notifications example 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). --- website/docs/docs/deploy/model-notifications.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/website/docs/docs/deploy/model-notifications.md b/website/docs/docs/deploy/model-notifications.md index 45ffbef0a4f..7396f67f14d 100644 --- a/website/docs/docs/deploy/model-notifications.md +++ b/website/docs/docs/deploy/model-notifications.md @@ -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: finance@dbtlabs.com favorite_food: donuts - name: marketing owner: - name: "Marketing Team" - description: "Models related to the marketing department" + name: "Marketing team" email: marketing@dbtlabs.com favorite_food: jaffles + + - name: docs + owner: + name: "Documentation team" + email: docs@dbtlabs.com + favorite_food: pizza ``` +:::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: