From 368b5f741647114b7332c1f509325e7c59788c9d Mon Sep 17 00:00:00 2001 From: bthomson22 Date: Wed, 25 Oct 2023 22:25:42 -0600 Subject: [PATCH 1/2] Fixed typo --- website/docs/docs/cloud/about-cloud-develop-defer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 1c0b316f885..84fd262ffab 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -39,7 +39,7 @@ The dbt Cloud CLI offers additional flexibility by letting you choose the source ```yml -dever-env-id: '123456' +defer-env-id: '123456' ``` @@ -49,7 +49,7 @@ dever-env-id: '123456' ```yml dbt_cloud: - dever-env-id: '123456' + defer-env-id: '123456' ``` From 8296a9039b6e7daf108aa69199381bd0f2831745 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 26 Oct 2023 10:15:47 +0100 Subject: [PATCH 2/2] Update about-cloud-develop-defer.md --- website/docs/docs/cloud/about-cloud-develop-defer.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 84fd262ffab..85bf20880f8 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -17,24 +17,24 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr - This can be set for one deployment environment per dbt Cloud project. - You must have a successful job run first. -When using 'defer', it compares artifacts from the most recent successful production job, excluding CI jobs. +When using defer, it compares artifacts from the most recent successful production job, excluding CI jobs. ### Defer in the dbt Cloud IDE -To enable 'Defer' in the dbt Cloud IDE, toggle the **Defer to production** button on the command bar. Once enabled, dbt Cloud will: +To enable defer in the dbt Cloud IDE, toggle the **Defer to production** button on the command bar. Once enabled, dbt Cloud will: 1. Pull down the most recent manifest from the Production environment for comparison 2. Pass the `--defer` flag to the command (for any command that accepts the flag) For example, if you were to start developing on a new branch with [nothing in your development schema](/reference/node-selection/defer#usage), edit a single model, and run `dbt build -s state:modified` — only the edited model would run. Any `{{ ref() }}` functions will point to the production location of the referenced models. - + ### Defer in dbt Cloud CLI -One key difference between using `--defer` in the dbt Cloud CLI and the dbt Cloud IDE is that `--defer` is *automatically* enabled in the dbt Cloud CLI for all invocations, comparing with production artifacts. You can disable it with the `--no-defer` flag. +One key difference between using `--defer` in the dbt Cloud CLI and the dbt Cloud IDE is that `--defer` is *automatically* enabled in the dbt Cloud CLI for all invocations, compared with production artifacts. You can disable it with the `--no-defer` flag. -The dbt Cloud CLI offers additional flexibility by letting you choose the source environment for deferral artifacts. You can set a `defer-env-id` key in either your `dbt_project.yml` or `dbt_cloud.yml` file. If you do not provide a `defer-env-id` setting, the dbt Cloud CLI will use artifacts from your dbt Cloud environment marked 'Production'. +The dbt Cloud CLI offers additional flexibility by letting you choose the source environment for deferral artifacts. You can set a `defer-env-id` key in either your `dbt_project.yml` or `dbt_cloud.yml` file. If you do not provide a `defer-env-id` setting, the dbt Cloud CLI will use artifacts from your dbt Cloud environment marked "Production".