From 01fac977af44b303c2e3624fc0fabc30081af889 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 15 Nov 2023 19:38:56 +0000 Subject: [PATCH 1/5] Update cloud-cli-installation.md adding --no-cache-dir as installation due to [caching convo](https://dbt-labs.slack.com/archives/C051TUB7S9W/p1700077007992369?thread_ts=1700008115.722329&cid=C051TUB7S9W) --- website/docs/docs/cloud/cloud-cli-installation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 896b3c92f75..b945bede160 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -193,13 +193,13 @@ We recommend using virtual environments (venv) to namespace `cloud-cli`. 2. Make sure you're in your virtual environment and run the following command to install the dbt Cloud CLI: ```bash - pip3 install dbt + pip install dbt --no-cache-dir ``` -3. (Optional) To revert back to dbt Core, first uninstall both the dbt Cloud CLI and dbt Core. Then reinstall dbt Core. +3. (Optional) To revert to dbt Core, first uninstall both the dbt Cloud CLI and dbt Core. Then reinstall dbt Core. ```bash - pip3 uninstall dbt-core dbt + pip uninstall dbt-core dbt pip install dbt-adapter_name --force-reinstall ``` From a3b4b5058f1a5b75fc3eb6cc0337b2ebe0a685a6 Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Wed, 15 Nov 2023 11:40:34 -0800 Subject: [PATCH 2/5] Dark mode icon --- website/docs/guides/microsoft-fabric-qs.md | 2 +- website/static/img/icons/white/fabric.svg | 62 ++++++++++++++++++++++ 2 files changed, 63 insertions(+), 1 deletion(-) create mode 100644 website/static/img/icons/white/fabric.svg diff --git a/website/docs/guides/microsoft-fabric-qs.md b/website/docs/guides/microsoft-fabric-qs.md index f27fcaa5c79..c7c53a2aac7 100644 --- a/website/docs/guides/microsoft-fabric-qs.md +++ b/website/docs/guides/microsoft-fabric-qs.md @@ -20,7 +20,7 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Microsoft Fabri :::tip Public preview -A public preview of dbt Cloud support for Microsoft Fabric in now available! +A public preview of Microsoft Fabric in dbt Cloud is now available! ::: diff --git a/website/static/img/icons/white/fabric.svg b/website/static/img/icons/white/fabric.svg new file mode 100644 index 00000000000..b03e8cb9d01 --- /dev/null +++ b/website/static/img/icons/white/fabric.svg @@ -0,0 +1,62 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From ac5ad7b73bbe53f092ab4c37d2ae8c46ec6886be Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Wed, 15 Nov 2023 14:40:50 -0700 Subject: [PATCH 3/5] Fix examples for `dbt deps --add-package` (#4470) [Preview](https://docs-getdbt-com-git-dbeatty-fix-dbt-deps-add-package-dbt-labs.vercel.app/reference/commands/deps) ## What are you changing in this pull request and why? Fixing the code examples per https://github.com/dbt-labs/dbt-core/issues/9076 by using test examples from https://github.com/dbt-labs/dbt-core/pull/8408 ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines. - [x] I've checked that the code examples work - [x] I've confirmed that the preview renders correctly --- website/docs/reference/commands/deps.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/website/docs/reference/commands/deps.md b/website/docs/reference/commands/deps.md index f4f8153c115..60ccd091ad7 100644 --- a/website/docs/reference/commands/deps.md +++ b/website/docs/reference/commands/deps.md @@ -60,28 +60,28 @@ Update your versions in packages.yml, then run dbt deps -dbt generates the `package-lock.yml` file in the _project_root_ where `packages.yml` is recorded, which contains all the resolved packages, the first time you run `dbt deps`. Each subsequent run records the packages installed in this file. If the subsequent `dbt deps` runs contain no updated packages in `depenedencies.yml` or `packages.yml`, dbt-core installs from `package-lock.yml`. +dbt generates the `package-lock.yml` file in the _project_root_ where `packages.yml` is recorded, which contains all the resolved packages, the first time you run `dbt deps`. Each subsequent run records the packages installed in this file. If the subsequent `dbt deps` runs contain no updated packages in `dependencies.yml` or `packages.yml`, dbt-core installs from `package-lock.yml`. When you update the package spec and run `dbt deps` again, the package-lock and package files update accordingly. You can run `dbt deps --lock` to update the `package-lock.yml` with the most recent dependencies from `packages`. -The `--add` flag allows you to add a package to the `packages.yml` with configurable `--version` and `--source` information. The `--dry-run` flag, when set to `False`(default), recompiles the `package-lock.yml` file after a new package is added to the `packages.yml` file. Set the flag to `True` for the changes to not persist. +The `--add-package` flag allows you to add a package to the `packages.yml` with configurable `--version` and `--source` information. The `--dry-run` flag, when set to `False`(default), recompiles the `package-lock.yml` file after a new package is added to the `packages.yml` file. Set the flag to `True` for the changes to not persist. -Examples of the `--add` flag: +Examples of the `--add-package` flag: ```shell # add package from hub (--source arg defaults to "hub") -dbt deps add --package dbt-labs/dbt_utils --version 1.0.0 +dbt deps --add-package dbt-labs/dbt_utils@1.0.0 -# add package from hub with semantic version -dbt deps add --package dbt-labs/snowplow --version ">=0.7.0,<0.8.0" +# add package from hub with semantic version range +dbt deps --add-package dbt-labs/snowplow@">=0.7.0,<0.8.0" # add package from git -dbt deps add --package https://github.com/fivetran/dbt_amplitude --version v0.3.0 --source git +dbt deps --add-package https://github.com/fivetran/dbt_amplitude@v0.3.0 --source git -# add package from local (--version not required for local) -dbt deps add --package /opt/dbt/redshift --source local +# add package from local +dbt deps --add-package /opt/dbt/redshift --source local -# add package to packages.yml WITHOUT updating package-lock.yml -dbt deps add --package dbt-labs/dbt_utils --version 1.0.0 --dry-run True +# add package to packages.yml and package-lock.yml WITHOUT actually installing dependencies +dbt deps --add-package dbt-labs/dbt_utils@1.0.0 --dry-run ``` - \ No newline at end of file + From 8694388caee89cd716e5950d07a8aba594ff25ac Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Wed, 15 Nov 2023 16:18:35 -0700 Subject: [PATCH 4/5] Fix config example for `dbt_project.yml` (#4443) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Previews - [Semantic models](https://docs-getdbt-com-git-dbeatty-semantic-model-conf-4886b9-dbt-labs.vercel.app/docs/build/semantic-models) ## What are you changing in this pull request and why? Within `dbt_project.yml`, resource types have dashes (`-`) instead of underscores (`_`), so we need to update this code example accordingly. ### Backstory Within the description for https://github.com/dbt-labs/docs.getdbt.com/issues/4180, I added some examples of what I _guessed_ the syntax would be, but I didn't specify that these were completely unverified guesses 😬. This particular example got missed during #4281. ### 🎩 image ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines. - [x] I have verified that the code examples work - [x] I have checked that the preview renders correctly --------- Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- website/docs/docs/build/semantic-models.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/build/semantic-models.md b/website/docs/docs/build/semantic-models.md index 118e93a26b1..99ccef237f9 100644 --- a/website/docs/docs/build/semantic-models.md +++ b/website/docs/docs/build/semantic-models.md @@ -123,14 +123,18 @@ semantic_models: config: enabled: true | false group: some_group + meta: + some_key: some_value ``` Semantic model config in `dbt_project.yml`: ```yml -semantic_models: +semantic-models: my_project_name: +enabled: true | false +group: some_group + +meta: + some_key: some_value ``` From 39ddb79244c38090d32993978d67476826589679 Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Wed, 15 Nov 2023 15:41:29 -0800 Subject: [PATCH 5/5] Update prereqs for CI and GitLab --- website/docs/docs/deploy/ci-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md index 6114ed1ca14..149a6951fdc 100644 --- a/website/docs/docs/deploy/ci-jobs.md +++ b/website/docs/docs/deploy/ci-jobs.md @@ -15,7 +15,7 @@ dbt Labs recommends that you create your CI job in a dedicated dbt Cloud [deploy - You have a dbt Cloud account. - For the [Concurrent CI checks](/docs/deploy/continuous-integration#concurrent-ci-checks) and [Smart cancellation of stale builds](/docs/deploy/continuous-integration#smart-cancellation) features, your dbt Cloud account must be on the [Team or Enterprise plan](https://www.getdbt.com/pricing/). - You must be connected using dbt Cloud’s native Git integration with [GitHub](/docs/cloud/git/connect-github), [GitLab](/docs/cloud/git/connect-gitlab), or [Azure DevOps](/docs/cloud/git/connect-azure-devops). - - If you’re using GitLab, you must use a paid or self-hosted account which includes support for GitLab webhooks. + - With GitLab, you need a paid or self-hosted account which includes support for GitLab webhooks and [project access tokens](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html). With GitLab Free, merge requests will invoke CI jobs but CI status updates (success or failure of the job) will not be reported back to GitLab. - If you previously configured your dbt project by providing a generic git URL that clones using SSH, you must reconfigure the project to connect through dbt Cloud's native integration.