Skip to content

Commit

Permalink
Merge branch 'current' into add-model-tag-example
Browse files Browse the repository at this point in the history
  • Loading branch information
mirnawong1 authored Jan 13, 2025
2 parents 10248cc + 95dfba3 commit 280fab9
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 13 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
26 changes: 16 additions & 10 deletions website/docs/docs/deploy/webhooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,17 +36,23 @@ 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.
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. 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.
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.

:::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 the webhooks list and click the reactivate button to enable it and continue receiving events.
:::

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.
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:
Expand Down
2 changes: 1 addition & 1 deletion website/docs/guides/snowflake-qs.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
5 changes: 4 additions & 1 deletion website/docs/reference/artifacts/run-results-json.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down

0 comments on commit 280fab9

Please sign in to comment.