From 8807ffda0af4ed2c8a81c4180076ec5f68ea633e Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Fri, 10 Jan 2025 13:10:31 +0000 Subject: [PATCH 1/7] add note about webhook limit --- website/docs/docs/deploy/webhooks.md | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/website/docs/docs/deploy/webhooks.md b/website/docs/docs/deploy/webhooks.md index 4ff9c350344..42f5d3039a5 100644 --- a/website/docs/docs/deploy/webhooks.md +++ b/website/docs/docs/deploy/webhooks.md @@ -36,17 +36,22 @@ You can also check out the free [dbt Fundamentals course](https://learn.getdbt.c ## Create a webhook subscription {#create-a-webhook-subscription} -Navigate to **Account settings** in dbt Cloud (by clicking your account name from the left side panel), and click **Create New Webhook** in the **Webhooks** section. You can find the appropriate dbt Cloud access URL for your region and plan with [Regions & IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses). - -To configure your new webhook: - -- **Name** — Enter a name for your outbound webhook. -- **Description** — Enter a description of the webhook. -- **Events** — Choose the event you want to trigger this webhook. You can subscribe to more than one event. -- **Jobs** — Specify the job(s) you want the webhook to trigger on. Or, you can leave this field empty for the webhook to trigger on all jobs in your account. By default, dbt Cloud configures your webhook at the account level. -- **Endpoint** — Enter your application's endpoint URL, where dbt Cloud can send the event(s) to. - -When done, click **Save**. dbt Cloud provides a secret token that you can use to [check for the authenticity of a webhook](#validate-a-webhook). It’s strongly recommended that you perform this check on your server to protect yourself from fake (spoofed) requests. +1. Navigate to **Account settings** in dbt Cloud (by clicking your account name from the left side panel) +2. Go to the **Webhooks** section and click **Create webhook**. +3. You can find the appropriate dbt Cloud access URL for your region and plan with [Regions & IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses). +4. To configure your new webhook: + - **Webhook name** — Enter a name for your outbound webhook. + - **Description** — Enter a description of the webhook. + - **Events** — Choose the event you want to trigger this webhook. You can subscribe to more than one event. + - **Jobs** — Specify the job(s) you want the webhook to trigger on. Or, you can leave this field empty for the webhook to trigger on all jobs in your account. By default, dbt Cloud configures your webhook at the account level. + - **Endpoint** — Enter your application's endpoint URL, where dbt Cloud can send the event(s) to. +5. When done, click **Save**. + + dbt Cloud provides a secret token that you can use to [check for the authenticity of a webhook](#validate-a-webhook). It’s strongly recommended that you perform this check on your server to protect yourself from fake (spoofed) requests. + +:::info +Note that dbt Cloud automatically deactivates a webhook after 5 consecutive failed attempts to send events to your endpoint. +::: ### Differences between completed and errored webhook events {#completed-errored-event-difference} The `job.run.errored` event is a subset of the `job.run.completed` events. If you subscribe to both, you will receive two notifications when your job encounters an error. However, dbt Cloud triggers the two events at different times: From ff5de283d837da407bef83c107debec7d5996111 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 10 Jan 2025 18:15:44 +0000 Subject: [PATCH 2/7] Update webhooks.md --- website/docs/docs/deploy/webhooks.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/deploy/webhooks.md b/website/docs/docs/deploy/webhooks.md index 42f5d3039a5..bc7ea86cb5c 100644 --- a/website/docs/docs/deploy/webhooks.md +++ b/website/docs/docs/deploy/webhooks.md @@ -38,14 +38,13 @@ You can also check out the free [dbt Fundamentals course](https://learn.getdbt.c 1. Navigate to **Account settings** in dbt Cloud (by clicking your account name from the left side panel) 2. Go to the **Webhooks** section and click **Create webhook**. -3. You can find the appropriate dbt Cloud access URL for your region and plan with [Regions & IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses). -4. To configure your new webhook: +3. To configure your new webhook: - **Webhook name** — Enter a name for your outbound webhook. - **Description** — Enter a description of the webhook. - **Events** — Choose the event you want to trigger this webhook. You can subscribe to more than one event. - **Jobs** — Specify the job(s) you want the webhook to trigger on. Or, you can leave this field empty for the webhook to trigger on all jobs in your account. By default, dbt Cloud configures your webhook at the account level. - **Endpoint** — Enter your application's endpoint URL, where dbt Cloud can send the event(s) to. -5. When done, click **Save**. +4. When done, click **Save**. dbt Cloud provides a secret token that you can use to [check for the authenticity of a webhook](#validate-a-webhook). It’s strongly recommended that you perform this check on your server to protect yourself from fake (spoofed) requests. @@ -53,6 +52,8 @@ You can also check out the free [dbt Fundamentals course](https://learn.getdbt.c Note that dbt Cloud automatically deactivates a webhook after 5 consecutive failed attempts to send events to your endpoint. ::: +To find the appropriate dbt Cloud access URL for your region and plan, refer to [Regions & IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses). + ### Differences between completed and errored webhook events {#completed-errored-event-difference} The `job.run.errored` event is a subset of the `job.run.completed` events. If you subscribe to both, you will receive two notifications when your job encounters an error. However, dbt Cloud triggers the two events at different times: From 319119bf5780788306e5e677d6726b9b8d964951 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 10 Jan 2025 19:16:19 +0000 Subject: [PATCH 3/7] Update website/docs/docs/deploy/webhooks.md --- website/docs/docs/deploy/webhooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/webhooks.md b/website/docs/docs/deploy/webhooks.md index bc7ea86cb5c..f7bd82b7916 100644 --- a/website/docs/docs/deploy/webhooks.md +++ b/website/docs/docs/deploy/webhooks.md @@ -49,7 +49,7 @@ You can also check out the free [dbt Fundamentals course](https://learn.getdbt.c dbt Cloud provides a secret token that you can use to [check for the authenticity of a webhook](#validate-a-webhook). It’s strongly recommended that you perform this check on your server to protect yourself from fake (spoofed) requests. :::info -Note that dbt Cloud automatically deactivates a webhook after 5 consecutive failed attempts to send events to your endpoint. +Note that dbt Cloud automatically deactivates a webhook after 5 consecutive failed attempts to send events to your endpoint. To re-activate the webhook, locate it in in the webhooks list and click the reactivate button to enable it and continue receiving events. ::: To find the appropriate dbt Cloud access URL for your region and plan, refer to [Regions & IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses). From 86d6d3733966916430f4be0b7f3483fb7cd79198 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 10 Jan 2025 19:16:43 +0000 Subject: [PATCH 4/7] Update website/docs/docs/deploy/webhooks.md --- website/docs/docs/deploy/webhooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/webhooks.md b/website/docs/docs/deploy/webhooks.md index f7bd82b7916..5aa8abbe41f 100644 --- a/website/docs/docs/deploy/webhooks.md +++ b/website/docs/docs/deploy/webhooks.md @@ -49,7 +49,7 @@ You can also check out the free [dbt Fundamentals course](https://learn.getdbt.c dbt Cloud provides a secret token that you can use to [check for the authenticity of a webhook](#validate-a-webhook). It’s strongly recommended that you perform this check on your server to protect yourself from fake (spoofed) requests. :::info -Note that dbt Cloud automatically deactivates a webhook after 5 consecutive failed attempts to send events to your endpoint. To re-activate the webhook, locate it in in the webhooks list and click the reactivate button to enable it and continue receiving events. +Note that dbt Cloud automatically deactivates a webhook after 5 consecutive failed attempts to send events to your endpoint. To re-activate the webhook, locate it in the webhooks list and click the reactivate button to enable it and continue receiving events. ::: To find the appropriate dbt Cloud access URL for your region and plan, refer to [Regions & IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses). From 258673c806884425639a7857e59d74e553529d66 Mon Sep 17 00:00:00 2001 From: Kshitij Aranke Date: Fri, 10 Jan 2025 20:50:29 +0000 Subject: [PATCH 5/7] Update run-results-json.md (#6762) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## What are you changing in this pull request and why? * Add more commands to produced by list * Bump latest version to v6 ## Checklist - [x] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. --- 🚀 Deployment available! Here are the direct links to the updated files: - https://docs-getdbt-com-git-update-run-results-dbt-labs.vercel.app/reference/artifacts/run-results-json --- website/docs/reference/artifacts/run-results-json.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/docs/reference/artifacts/run-results-json.md b/website/docs/reference/artifacts/run-results-json.md index 13ad528d185..118b5615ea8 100644 --- a/website/docs/reference/artifacts/run-results-json.md +++ b/website/docs/reference/artifacts/run-results-json.md @@ -3,14 +3,17 @@ title: "Run results JSON file" sidebar_label: "Run results" --- -**Current schema**: [`v5`](https://schemas.getdbt.com/dbt/run-results/v5/index.html) +**Current schema**: [`v6`](https://schemas.getdbt.com/dbt/run-results/v6/index.html) **Produced by:** [`build`](/reference/commands/build) + [`clone`](/reference/commands/clone) [`compile`](/reference/commands/compile) [`docs generate`](/reference/commands/cmd-docs) + [`retry`](/reference/commands/retry) [`run`](/reference/commands/run) [`seed`](/reference/commands/seed) + [`show`](/reference/commands/show) [`snapshot`](/reference/commands/snapshot) [`test`](/reference/commands/test) [`run-operation`](/reference/commands/run-operation) From ab53100c9828e9d099e930a4672135687217a46c Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 10 Jan 2025 20:59:07 +0000 Subject: [PATCH 6/7] Update 06-upgrading-to-v1.9.md (#6761) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ths pr documents the regressiong/breaking change for dbt-snowflake users when migrating from 1.8 to 1.9 Resolves #6759 --- 🚀 Deployment available! Here are the direct links to the updated files: - https://docs-getdbt-com-git-mirnawong1-patch-26-dbt-labs.vercel.app/docs/dbt-versions/core-upgrade/upgrading-to-v1.9#snowflake Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- .../docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md b/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md index 2a4a9d96528..6009fc4c73a 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md +++ b/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md @@ -103,7 +103,8 @@ You can read more about each of these behavior changes in the following links: ### Snowflake -- Iceberg Table Format support will be available on three out-of-the-box materializations: table, incremental, dynamic tables. +- Iceberg Table Format — Support will be available on three out-of-the-box materializations: table, incremental, dynamic tables. +- Breaking change — When upgrading from dbt 1.8 to 1.9 `{{ target.account }}` replaces underscores with dashes. For example, if the `target.account` is set to `sample_company`, then the compiled code now generates `sample-company`. [Refer to the `dbt-snowflake` issue](https://github.com/dbt-labs/dbt-snowflake/issues/1286) for more information. ### Bigquery From 95dfba3e5406653232f132d9b9adeda3e90e1efc Mon Sep 17 00:00:00 2001 From: faithebear <149540831+faithebear@users.noreply.github.com> Date: Fri, 10 Jan 2025 16:43:55 -0700 Subject: [PATCH 7/7] Update snowflake-qs.md (#6763) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## What are you changing in this pull request and why? update snowflake quickstart to reflect new way to make a worksheet ## Checklist - [x] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [x] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and/or [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content) guidelines. - [x] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." - [x] The content in this PR requires a dbt release note, so I added one to the [release notes page](https://docs.getdbt.com/docs/dbt-versions/dbt-cloud-release-notes). --- 🚀 Deployment available! Here are the direct links to the updated files: - https://docs-getdbt-com-git-faithebear-patch-1-dbt-labs.vercel.app/guides/snowflake-qs --------- Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/guides/snowflake-qs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/snowflake-qs.md b/website/docs/guides/snowflake-qs.md index 40bdeed1ef2..18e77ce050c 100644 --- a/website/docs/guides/snowflake-qs.md +++ b/website/docs/guides/snowflake-qs.md @@ -46,7 +46,7 @@ You can also watch the [YouTube video on dbt and Snowflake](https://www.youtube. ## Create a new Snowflake worksheet 1. Log in to your trial Snowflake account. -2. In the Snowflake UI, click **+ Worksheet** in the upper right corner to create a new worksheet. +2. In the Snowflake UI, click **+ Create** in the left-hand corner, underneath the Snowflake logo, which opens a dropdown. Select the first option, **SQL Worksheet**. ## Load data The data used here is stored as CSV files in a public S3 bucket and the following steps will guide you through how to prepare your Snowflake account for that data and upload it.