From 28c28c81fb9b6ad380effb07a48675be4f181880 Mon Sep 17 00:00:00 2001 From: rpourzand Date: Mon, 23 Oct 2023 15:30:18 -0700 Subject: [PATCH 01/33] Update sl-partner-integration-guide.md Adding a note on best practices for putting metadata in API requests for integration partners --- .../sl-partner-integration-guide.md | 27 ++++++++++++------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index c41469bf08a..ad341eb4eff 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -33,6 +33,14 @@ The dbt Semantic Layer APIs authenticate with `environmentId`, `SERVICE_TOKEN`, We recommend you provide users with separate input fields with these components for authentication (dbt Cloud will surface these parameters for the user). +### Exposing Metadata to dbt Labs + +When building an integration, we recommend you expose certain metadata in the request for analytics purposes. Among other items, it is helpful to have the following: + +- Your application's name (e.g., Tableau) +- The user email of the person querying from your application +- The version of dbt they are on. + ## Best practices on exposing metrics @@ -85,7 +93,7 @@ Allow users to query either one metric alone without dimensions or multiple metr - Allow toggling between metrics/dimensions seamlessly. -- Be clear on exposing what dimensions are queryable with what metrics and hide things that don’t apply, and vice versa. +- Be clear on exposing what dimensions are queryable with what metrics and hide things that don’t apply(our APIs provide calls for you to get relevant dimensions for metrics, and vice versa). - Only expose time granularities (monthly, daily, yearly) that match the available metrics. * For example, if a dbt model and its resulting semantic model have a monthly granularity, make sure querying data with a 'daily' granularity isn't available to the user. Our APIs have functionality that will help you surface the correct granularities @@ -109,6 +117,15 @@ For better analysis, it's best to have the context of the metrics close to where - Allow for creating other metadata that’s useful for the metric. We can provide some of this information in our configuration (Display name, Default Granularity for View, Default Time range), but there may be other metadata that your tool wants to provide to make the metric richer. +### Transparency and Using Compile + +For transparency and additional context, we recommend you have an easy way for the user to obtain the SQL that MetricFlow generates. Depending on what API you are using, you can do this by using our compile parameter. This is incredibly powerful because we want to be very transparent to the user about what we're doing and do not want to be a black box. This would be mostly beneficial to a technical user. + + +### Where filters and Optimization + +In the cases where our APIs support either a string or a filter list for the `where` clause, we always recommend that your application utilizes the filter list in order to gain maximum pushdown benefits. The `where` string may be more intuitive for users writing queries during testing, but it will not have the performance benefits of the filter list in a production environment. + ## Example stages of an integration These are recommendations on how to evolve a Semantic Layer integration and not a strict runbook. @@ -136,14 +153,6 @@ These are recommendations on how to evolve a Semantic Layer integration and not * Querying dimensions without metrics and other more advanced querying functionality * Suggest metrics to users based on teams/identity, and so on. -### A note on transparency and using compile - -For transparency and additional context, we recommend you have an easy way for the user to obtain the SQL that MetricFlow generates. Depending on what API you are using, you can do this by using our compile parameter. This is incredibly powerful because we want to be very transparent to the user about what we're doing and do not want to be a black box. This would be mostly beneficial to a technical user. - - -### A note on where filters - -In the cases where our APIs support either a string or a filter list for the `where` clause, we always recommend that your application utilizes the filter list in order to gain maximum pushdown benefits. The `where` string may be more intuitive for users writing queries during testing, but it will not have the performance benefits of the filter list in a production environment. ## Related docs From 953d748b1867895dfed7db0d1d65e060476b4ea8 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Tue, 24 Oct 2023 12:12:26 +0100 Subject: [PATCH 02/33] adding steve's video --- .../docs/docs/cloud/cloud-cli-installation.md | 80 +++++++++++++------ 1 file changed, 54 insertions(+), 26 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 5c0d6ad543e..da651156303 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -29,7 +29,7 @@ You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/db ## Install dbt Cloud CLI -You can install the dbt Cloud CLI on the command line by using one of these methods: +You can install the dbt Cloud CLI on the command line by using one of these methods. For a video instruction step-by-step guide, refer to the [FAQs](#faqs). @@ -38,24 +38,35 @@ You can install the dbt Cloud CLI on the command line by using one of these meth Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in your code editor or command line terminal. Refer to the [FAQs](#faqs) if your operating system runs into path conflicts. -1. Run the following command to verify that there is no conflict with a dbt Core installation on your system: +1. Run the following command to verify that you don't already have dbt Core installed: ```bash which dbt ``` - - This should return a `dbt not found`. If the dbt help text appears, use `pip uninstall dbt` to deactivate dbt Core from your machine. + - This should return a `dbt not found`. If the dbt help text appears, use `pip uninstall dbt` to remove dbt Core from your machine.
2. Install the dbt Cloud CLI with Homebrew: - ```bash - brew untap dbt-labs/dbt - brew tap dbt-labs/dbt-cli - brew install dbt - ``` - -3. Verify the installation by running `dbt --help` from the command line. If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. + - First, remove a tap, which is like a separate repository for packages, from Homebrew. This stops Homebrew from installing packages from that repository: + ```bash + brew untap dbt-labs/dbt + - Then run `brew tap` to add and install the dbt Cloud CLI as a package: + ```bash + brew tap dbt-labs/dbt-cli + ``` + - Lastly, install the dbt Cloud CLI with Homebrew: + ```bash + brew install dbt + ``` + +3. Verify the installation by running `dbt --help` from the command line. + * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a global dbt version installed. * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. +4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. + +**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + @@ -73,9 +84,14 @@ Advanced users can configure multiple projects to use the same dbt Cloud CLI by Note that if you are using VS Code, you must restart it to pick up modified environment variables. ::: -3. Verify the installation by running `./dbt --help` from the command line. If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. +3. Verify the installation by running `./dbt --help` from the command line. + * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. +4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. + +**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + @@ -97,23 +113,32 @@ Advanced users can configure multiple projects to use the same Cloud CLI executa ::: -3. Verify the installation by running `./dbt --help` from the command line. If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. +3. Verify the installation by running `./dbt --help` from the command line. + * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. +4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. + +**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + -:::info Use native packages or a virtual environment to avoid overriding dbt Core -Installing the dbt Cloud CLI with pip replaces dbt Core. This change can be avoided by using the native install method and configuring your PATH or by creating a new virtual environment. +:::info Use native packages or a virtual environment to prevent dbt Core conflicts -Otherwise, to switch back to dbt Core, uninstall the dbt Cloud CLI and follow the dbt Core installation instructions. +To prevent overwriting dbt Core, avoid installing the dbt Cloud CLI with pip. Instead, consider using the native installation method and configuring your PATH or create a new virtual environment. + +If you've already installed the dbt Cloud CLI and need to switch back to dbt Core, uninstall the dbt Cloud CLI, and follow the dbt Core installation instructions. + +You can also have both dbt Cloud CLI and dbt Core installed simultaneously. To avoid conflicts, alias the dbt Cloud CLI as `dbt-cloud`. For more details, check the [FAQs](#faqs) if your operating system experiences path conflicts. +::: -::: Before installing the dbt Cloud CLI, make sure you have Python installed and your virtual environment venv or pyenv . If you already have a Python environment configured, you can skip to the [pip installation step](#install-dbt-cloud-cli-in-pip). + ### Install a virtual environment We recommend using virtual environments (venv) to namespace `cloud-cli`. @@ -156,6 +181,10 @@ We recommend using virtual environments (venv) to namespace `cloud-cli`. pip3 install dbt-core==VERSION ``` +4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. + +**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + @@ -198,16 +227,6 @@ To update: - -## Next steps - -After installation, you can [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. - -For example, you can execute `dbt compile` to compile a project using dbt Cloud. - -Note, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. - - ## FAQs
@@ -231,3 +250,12 @@ If you have dbt Core installed locally, either: You can always uninstall the dbt Cloud CLI to return to using dbt Core.
+ +
+Are there any instructional videos to help guide me through installation? +For a video walkthrough of the installation process, refer to the following video: + + + +
+ From a3894dc96ec4379dc48c1126aacffd7efdc22d04 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 24 Oct 2023 15:51:36 +0100 Subject: [PATCH 03/33] Update website/docs/docs/cloud/cloud-cli-installation.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index da651156303..e921c629bb0 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -29,7 +29,7 @@ You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/db ## Install dbt Cloud CLI -You can install the dbt Cloud CLI on the command line by using one of these methods. For a video instruction step-by-step guide, refer to the [FAQs](#faqs). +You can install the dbt Cloud CLI on the command line by using one of these methods. For a step-by-step video guide, refer to the [FAQs](#faqs). From 640e75871e417b4e6d15a02402a03ebdbee069f5 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 24 Oct 2023 15:58:39 +0100 Subject: [PATCH 04/33] Update website/docs/docs/cloud/cloud-cli-installation.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index e921c629bb0..0d8e234c698 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -47,7 +47,7 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo 2. Install the dbt Cloud CLI with Homebrew: - - First, remove a tap, which is like a separate repository for packages, from Homebrew. This stops Homebrew from installing packages from that repository: + - First, remove the dbt-labs tap, the separate repository for packages, from Homebrew. This prevents Homebrew from installing packages from that repository: ```bash brew untap dbt-labs/dbt - Then run `brew tap` to add and install the dbt Cloud CLI as a package: From 22280372d930bd23480d62ae3ca836884fc66a5a Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 24 Oct 2023 16:09:34 +0100 Subject: [PATCH 05/33] Update website/docs/docs/cloud/cloud-cli-installation.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 0d8e234c698..da6c5c53197 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -63,7 +63,7 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a global dbt version installed. * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. -4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. +4. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. **Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. From c8e066aa645892515e0f2564cac9b71f9559f1cd Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 24 Oct 2023 16:11:30 +0100 Subject: [PATCH 06/33] Update website/docs/docs/cloud/cloud-cli-installation.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index da6c5c53197..51cf9482cc0 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -65,7 +65,7 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo 4. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. -**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. +If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. From 36facee9fea9b3a95e68d201b08fc160e20c1821 Mon Sep 17 00:00:00 2001 From: Brian Jan Date: Tue, 24 Oct 2023 15:32:53 -0500 Subject: [PATCH 07/33] Update set-up-sso-okta.md Added expiring cert note --- website/docs/docs/cloud/manage-access/set-up-sso-okta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/manage-access/set-up-sso-okta.md b/website/docs/docs/cloud/manage-access/set-up-sso-okta.md index 5ec70443d1f..c5328695fe2 100644 --- a/website/docs/docs/cloud/manage-access/set-up-sso-okta.md +++ b/website/docs/docs/cloud/manage-access/set-up-sso-okta.md @@ -171,7 +171,7 @@ configured in the steps above. | **Log in with** | Okta | | **Identity Provider SSO Url** | Paste the **Identity Provider Single Sign-On URL** shown in the Okta setup instructions | | **Identity Provider Issuer** | Paste the **Identity Provider Issuer** shown in the Okta setup instructions | -| **X.509 Certificate** | Paste the **X.509 Certificate** shown in the Okta setup instructions | +| **X.509 Certificate** | Paste the **X.509 Certificate** shown in the Okta setup instructions; **Note:** When the cerificate expires, an Okta admin will have to generate a new one to be pasted into dbt Cloud for uninterrupted application access | | **Slug** | Enter your desired login slug. Users will be able to log into dbt Cloud by navigating to `https://YOUR_ACCESS_URL/enterprise-login/LOGIN-SLUG`, replacing `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan. Login slugs must be unique across all dbt Cloud accounts, so pick a slug that uniquely identifies your company. | Date: Tue, 24 Oct 2023 15:45:29 -0700 Subject: [PATCH 08/33] Update tableau.md --- website/docs/docs/use-dbt-semantic-layer/tableau.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/tableau.md b/website/docs/docs/use-dbt-semantic-layer/tableau.md index ac3e6b64ab0..2eba9d0c318 100644 --- a/website/docs/docs/use-dbt-semantic-layer/tableau.md +++ b/website/docs/docs/use-dbt-semantic-layer/tableau.md @@ -15,7 +15,7 @@ The Tableau integration allows you to use worksheets to query the Semantic Layer ## Prerequisites 1. You must have [Tableau Desktop](https://www.tableau.com/en-gb/products/desktop) installed -2. Authenticate with either Tableau Server or Tableau Cloud +2. Authenticate in Tableau Desktop (you can authenticate with a license, or credentials used to login to Tableau Server or Online) 3. You need your dbt Cloud host, [Environment ID](/docs/use-dbt-semantic-layer/setup-sl#set-up-dbt-semantic-layer) and [service token](/docs/dbt-cloud-apis/service-tokens) to log in. This account should be set up with the dbt Semantic Layer. 4. You must a dbt Cloud Team or Enterprise [account](https://www.getdbt.com/pricing) and multi-tenant [deployment](/docs/cloud/about-cloud/regions-ip-addresses). (Single-Tenant coming soon) From 76568550363462ee816e6be21624e566aefd6c95 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 10:16:32 +0100 Subject: [PATCH 09/33] Update cloud-cli-installation.md clarify dbt --help output per Matt's feedbakc --- website/docs/docs/cloud/cloud-cli-installation.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 51cf9482cc0..d5e9904f137 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -23,7 +23,7 @@ dbt commands are run against dbt Cloud's infrastructure and benefit from: ## Prerequisites -The dbt Cloud CLI is available in all [deployment regions](/docs/cloud/about-cloud/regions-ip-addresses) and and for both multi-tenant and single-tenant accounts (Azure single-tenant not supported at this time). +The dbt Cloud CLI is available in all [deployment regions](/docs/cloud/about-cloud/regions-ip-addresses) and for both multi-tenant and single-tenant accounts (Azure single-tenant not supported at this time). You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-core-in-cloud) to upgrade. @@ -59,11 +59,16 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo brew install dbt ``` -3. Verify the installation by running `dbt --help` from the command line. - * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a global dbt version installed. - * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. +3. To verify your installation, open the command line and run the command dbt --help. If your installation is correct, you should see the following output: + ```bash + The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud. For more documentation on these commands, visit: docs.getdbt.com + ``` + This output confirms that you've successfully installed the dbt Cloud CLI. If you don't see this output, please ensure that you've deactivated your pyenv or venv and don't have a global dbt version + installed. + +Note that you no longer need to run the `dbt deps` command when your environment starts. This command was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. -4. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. +7. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. From f58614c0c87fa83ec94b489ed19a40884d1560a4 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 10:16:56 +0100 Subject: [PATCH 10/33] Update cloud-cli-installation.md --- website/docs/docs/cloud/cloud-cli-installation.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index d5e9904f137..928c7240080 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -63,8 +63,7 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo ```bash The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud. For more documentation on these commands, visit: docs.getdbt.com ``` - This output confirms that you've successfully installed the dbt Cloud CLI. If you don't see this output, please ensure that you've deactivated your pyenv or venv and don't have a global dbt version - installed. + This output confirms that you've successfully installed the dbt Cloud CLI. If you don't see this output, please ensure that you've deactivated your pyenv or venv and don't have a global dbt version installed. Note that you no longer need to run the `dbt deps` command when your environment starts. This command was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. From c3f50c96acbfc817f417882a1dac8de131d9c434 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 25 Oct 2023 10:32:18 +0100 Subject: [PATCH 11/33] rephrase --- .../docs/docs/cloud/cloud-cli-installation.md | 55 +++++++++++-------- 1 file changed, 32 insertions(+), 23 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 928c7240080..95962b0d8d9 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -19,7 +19,7 @@ dbt commands are run against dbt Cloud's infrastructure and benefit from: * [Automatic deferral](/docs/cloud/about-cloud-develop-defer) of build artifacts to your Cloud project's production environment. * Speedier, lower-cost builds. * Support for dbt Mesh ([cross-project `ref`](/docs/collaborate/govern/project-dependencies)), -* Significant platform improvements, to be released over the coming months. +https://github.com/dbt-labs/docs.getdbt.com/pull/4320* Significant platform improvements, to be released over the coming months. ## Prerequisites @@ -29,7 +29,9 @@ You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/db ## Install dbt Cloud CLI -You can install the dbt Cloud CLI on the command line by using one of these methods. For a step-by-step video guide, refer to the [FAQs](#faqs). +You can install the dbt Cloud CLI on the command line by using one of these methods. + +For a step-by-step video guide, refer to the [FAQs](#faqs). @@ -59,17 +61,17 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo brew install dbt ``` -3. To verify your installation, open the command line and run the command dbt --help. If your installation is correct, you should see the following output: - ```bash - The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud. For more documentation on these commands, visit: docs.getdbt.com - ``` - This output confirms that you've successfully installed the dbt Cloud CLI. If you don't see this output, please ensure that you've deactivated your pyenv or venv and don't have a global dbt version installed. - -Note that you no longer need to run the `dbt deps` command when your environment starts. This command was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. +3. Verify your installation by running `dbt --help` in the command line. If you see the following output, your installation is correct + ```bash + The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud... + ``` -7. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. + If you don't see this output, check that you've deactivated pyenv or venv and don't have a global dbt version installed. + + * Note that you no longer need to run the `dbt deps` command when your environment starts. This step was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. -If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. +4. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. @@ -88,13 +90,17 @@ Advanced users can configure multiple projects to use the same dbt Cloud CLI by Note that if you are using VS Code, you must restart it to pick up modified environment variables. ::: -3. Verify the installation by running `./dbt --help` from the command line. - * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. - * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. +3. Verify your installation by running `./dbt --help` in the command line. If you see the following output, your installation is correct + ```bash + The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud... + ``` -4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. + If you don't see this output, check that you've deactivated pyenv or venv and don't have a global dbt version installed. + + * Note that you no longer need to run the `dbt deps` command when your environment starts. This step was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. -**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. +4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. @@ -117,13 +123,17 @@ Advanced users can configure multiple projects to use the same Cloud CLI executa ::: -3. Verify the installation by running `./dbt --help` from the command line. - * If the help text doesn't indicate that you're using the dbt Cloud CLI, make sure you've deactivated your pyenv or venv and don't have a version of dbt globally installed. - * You don't have to run the `dbt deps` command when your environment starts. Previously, you had to do it during initialization. However, you'll still need to run `dbt deps` if you make changes to your `packages.yml` file. +3. Verify your installation by running `./dbt --help` in the command line. If you see the following output, your installation is correct + ```bash + The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud... + ``` + + If you don't see this output, check that you've deactivated pyenv or venv and don't have a global dbt version installed. + + * Note that you no longer need to run the `dbt deps` command when your environment starts. This step was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. 4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. - -**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. @@ -186,8 +196,7 @@ We recommend using virtual environments (venv) to namespace `cloud-cli`. ``` 4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. - -**Note**, that if you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. From 7bd3568bc744eacb8aa0ffe56a5cb5a43f2b2f17 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 25 Oct 2023 10:37:31 +0100 Subject: [PATCH 12/33] fold in feedback --- 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 95962b0d8d9..b0207b62dad 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -100,7 +100,7 @@ Note that if you are using VS Code, you must restart it to pick up modified envi * Note that you no longer need to run the `dbt deps` command when your environment starts. This step was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. 4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. - * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. @@ -133,7 +133,7 @@ Advanced users can configure multiple projects to use the same Cloud CLI executa * Note that you no longer need to run the `dbt deps` command when your environment starts. This step was previously required during initialization. However, you should still run `dbt deps` if you make any changes to your `packages.yml` file. 4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. - * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. @@ -196,7 +196,7 @@ We recommend using virtual environments (venv) to namespace `cloud-cli`. ``` 4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. - * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. + * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. From 7a38dbd9d9e5727faf7438635cfff391083e317d Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 10:39:20 +0100 Subject: [PATCH 13/33] Update website/docs/docs/cloud/cloud-cli-installation.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index b0207b62dad..f0628e08ec5 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -195,7 +195,7 @@ We recommend using virtual environments (venv) to namespace `cloud-cli`. pip3 install dbt-core==VERSION ``` -4. After installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile`, to compile a project using dbt Cloud and confirm that it works. +4. After you've verified the installation, [configure](/docs/cloud/configure-cloud-cli) the dbt Cloud CLI for your dbt Cloud project and use it to run [dbt commands](/reference/dbt-commands) similar to dbt Core. For example, execute `dbt compile` to compile a project using dbt Cloud and validate your models and tests. * If you're using the dbt Cloud CLI, you can connect to your data platform directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file locally on your machine. From 3ca3da318b7e6b7e0e6c4a36885e8deb169e8c81 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 25 Oct 2023 10:41:34 +0100 Subject: [PATCH 14/33] add colon --- 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 b0207b62dad..698dc92df20 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -61,7 +61,7 @@ Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in yo brew install dbt ``` -3. Verify your installation by running `dbt --help` in the command line. If you see the following output, your installation is correct +3. Verify your installation by running `dbt --help` in the command line. If you see the following output, your installation is correct: ```bash The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud... ``` @@ -90,7 +90,7 @@ Advanced users can configure multiple projects to use the same dbt Cloud CLI by Note that if you are using VS Code, you must restart it to pick up modified environment variables. ::: -3. Verify your installation by running `./dbt --help` in the command line. If you see the following output, your installation is correct +3. Verify your installation by running `./dbt --help` in the command line. If you see the following output, your installation is correct: ```bash The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud... ``` @@ -123,7 +123,7 @@ Advanced users can configure multiple projects to use the same Cloud CLI executa ::: -3. Verify your installation by running `./dbt --help` in the command line. If you see the following output, your installation is correct +3. Verify your installation by running `./dbt --help` in the command line. If you see the following output, your installation is correct: ```bash The dbt Cloud CLI - an ELT tool for running SQL transformations and data models in dbt Cloud... ``` From 736868a95acb0bc15fb9ebb2cc209ffa5adc037b Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:11:29 +0100 Subject: [PATCH 15/33] Update cloud-cli-installation.md folding privatelink/ssh per [slack thread](https://dbt-labs.slack.com/archives/C051TUB7S9W/p1698164950851459?thread_ts=1698149556.814129&cid=C051TUB7S9W) in this pr --- .../docs/docs/cloud/cloud-cli-installation.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index bd8be96a416..5816cff456e 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -25,13 +25,21 @@ https://github.com/dbt-labs/docs.getdbt.com/pull/4320* Significant platform impr ## Prerequisites The dbt Cloud CLI is available in all [deployment regions](/docs/cloud/about-cloud/regions-ip-addresses) and for both multi-tenant and single-tenant accounts (Azure single-tenant not supported at this time). -You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-core-in-cloud) to upgrade. +- Ensure you are using dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-core-in-cloud) to upgrade. +- Avoid using SSH tunneling for [Postgres and Redshift](/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb) connections. +- Avoid using [PrivateLink](/cloud/secure/about-privatelink). ## Install dbt Cloud CLI You can install the dbt Cloud CLI on the command line by using one of these methods. -For a step-by-step video guide, refer to the [FAQs](#faqs). +
+Watch a step-by-step video guide +For a video walkthrough of the installation process, refer to the following video: + + + +
@@ -39,7 +47,6 @@ For a step-by-step video guide, refer to the [FAQs](#faqs). Before you begin, make sure you have [Homebrew installed](http://brew.sh/) in your code editor or command line terminal. Refer to the [FAQs](#faqs) if your operating system runs into path conflicts. - 1. Run the following command to verify that you don't already have dbt Core installed: ```bash @@ -264,11 +271,4 @@ If you have dbt Core installed locally, either: You can always uninstall the dbt Cloud CLI to return to using dbt Core. -
-Are there any instructional videos to help guide me through installation? -For a video walkthrough of the installation process, refer to the following video: - - - -
From dabee4996653e67013f2e0a150a8a230d4d403c7 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:12:49 +0100 Subject: [PATCH 16/33] Update website/docs/docs/cloud/manage-access/set-up-sso-okta.md --- website/docs/docs/cloud/manage-access/set-up-sso-okta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/manage-access/set-up-sso-okta.md b/website/docs/docs/cloud/manage-access/set-up-sso-okta.md index c5328695fe2..cae592d2827 100644 --- a/website/docs/docs/cloud/manage-access/set-up-sso-okta.md +++ b/website/docs/docs/cloud/manage-access/set-up-sso-okta.md @@ -171,7 +171,7 @@ configured in the steps above. | **Log in with** | Okta | | **Identity Provider SSO Url** | Paste the **Identity Provider Single Sign-On URL** shown in the Okta setup instructions | | **Identity Provider Issuer** | Paste the **Identity Provider Issuer** shown in the Okta setup instructions | -| **X.509 Certificate** | Paste the **X.509 Certificate** shown in the Okta setup instructions; **Note:** When the cerificate expires, an Okta admin will have to generate a new one to be pasted into dbt Cloud for uninterrupted application access | +| **X.509 Certificate** | Paste the **X.509 Certificate** shown in the Okta setup instructions; **Note:** When the certificate expires, an Okta admin will have to generate a new one to be pasted into dbt Cloud for uninterrupted application access | | **Slug** | Enter your desired login slug. Users will be able to log into dbt Cloud by navigating to `https://YOUR_ACCESS_URL/enterprise-login/LOGIN-SLUG`, replacing `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan. Login slugs must be unique across all dbt Cloud accounts, so pick a slug that uniquely identifies your company. | Date: Wed, 25 Oct 2023 11:20:27 +0100 Subject: [PATCH 17/33] tweak video callout --- website/docs/docs/cloud/cloud-cli-installation.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 5816cff456e..5ce10b08355 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -34,8 +34,7 @@ The dbt Cloud CLI is available in all [deployment regions](/docs/cloud/about-clo You can install the dbt Cloud CLI on the command line by using one of these methods.
-Watch a step-by-step video guide -For a video walkthrough of the installation process, refer to the following video: +View a video tutorial for a step-by-step guide to installing From baf071595972a90c806eb84461951e8a2e455df6 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:25:47 +0100 Subject: [PATCH 18/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index ad341eb4eff..51cd9682502 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -33,7 +33,7 @@ The dbt Semantic Layer APIs authenticate with `environmentId`, `SERVICE_TOKEN`, We recommend you provide users with separate input fields with these components for authentication (dbt Cloud will surface these parameters for the user). -### Exposing Metadata to dbt Labs +### Exposing metadata to dbt Labs When building an integration, we recommend you expose certain metadata in the request for analytics purposes. Among other items, it is helpful to have the following: From 0122e225b54dbf4052685522cd18900fff7cb629 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:26:19 +0100 Subject: [PATCH 19/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 51cd9682502..fe2a1407c74 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -37,7 +37,7 @@ We recommend you provide users with separate input fields with these components When building an integration, we recommend you expose certain metadata in the request for analytics purposes. Among other items, it is helpful to have the following: -- Your application's name (e.g., Tableau) +- Your application's name (such as 'Tableau') - The user email of the person querying from your application - The version of dbt they are on. From 184ee98cabdc9077d5996d776e965a1574f450f3 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:26:58 +0100 Subject: [PATCH 20/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index fe2a1407c74..6c1751264cc 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -38,7 +38,7 @@ We recommend you provide users with separate input fields with these components When building an integration, we recommend you expose certain metadata in the request for analytics purposes. Among other items, it is helpful to have the following: - Your application's name (such as 'Tableau') -- The user email of the person querying from your application +- The email of the person querying your application - The version of dbt they are on. From af3b12b3e3c0d2bf6479053568a066bd9b1f793d Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:27:27 +0100 Subject: [PATCH 21/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 6c1751264cc..5b75498a4fd 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -93,7 +93,7 @@ Allow users to query either one metric alone without dimensions or multiple metr - Allow toggling between metrics/dimensions seamlessly. -- Be clear on exposing what dimensions are queryable with what metrics and hide things that don’t apply(our APIs provide calls for you to get relevant dimensions for metrics, and vice versa). +- Be clear on exposing what dimensions are queryable with what metrics and hide things that don’t apply. (Our APIs provide calls for you to get relevant dimensions for metrics, and vice versa). - Only expose time granularities (monthly, daily, yearly) that match the available metrics. * For example, if a dbt model and its resulting semantic model have a monthly granularity, make sure querying data with a 'daily' granularity isn't available to the user. Our APIs have functionality that will help you surface the correct granularities From 8a6abbb1fd3a05a4651dba603a01a57bccc20a4f Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:27:40 +0100 Subject: [PATCH 22/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 5b75498a4fd..bf40d43a8f0 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -117,7 +117,7 @@ For better analysis, it's best to have the context of the metrics close to where - Allow for creating other metadata that’s useful for the metric. We can provide some of this information in our configuration (Display name, Default Granularity for View, Default Time range), but there may be other metadata that your tool wants to provide to make the metric richer. -### Transparency and Using Compile +### Transparency and using compile For transparency and additional context, we recommend you have an easy way for the user to obtain the SQL that MetricFlow generates. Depending on what API you are using, you can do this by using our compile parameter. This is incredibly powerful because we want to be very transparent to the user about what we're doing and do not want to be a black box. This would be mostly beneficial to a technical user. From 2ed88fb71b14af5d6552b01c9b89eee758bff3a9 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:30:13 +0100 Subject: [PATCH 23/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index bf40d43a8f0..4f0f974ecf6 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -119,7 +119,7 @@ For better analysis, it's best to have the context of the metrics close to where ### Transparency and using compile -For transparency and additional context, we recommend you have an easy way for the user to obtain the SQL that MetricFlow generates. Depending on what API you are using, you can do this by using our compile parameter. This is incredibly powerful because we want to be very transparent to the user about what we're doing and do not want to be a black box. This would be mostly beneficial to a technical user. +For transparency and additional context, we recommend you have an easy way for the user to obtain the SQL that MetricFlow generates. Depending on what API you are using, you can do this by using our `compile` parameter. This is incredibly powerful and emphasizes transparency and openness, particularly for technically inclined users. ### Where filters and Optimization From 2212c4893191eed9041fc406034d40d48cd6ad95 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:30:39 +0100 Subject: [PATCH 24/33] Update website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index 4f0f974ecf6..b8041a5d197 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -122,7 +122,7 @@ For better analysis, it's best to have the context of the metrics close to where For transparency and additional context, we recommend you have an easy way for the user to obtain the SQL that MetricFlow generates. Depending on what API you are using, you can do this by using our `compile` parameter. This is incredibly powerful and emphasizes transparency and openness, particularly for technically inclined users. -### Where filters and Optimization +### Where filters and optimization In the cases where our APIs support either a string or a filter list for the `where` clause, we always recommend that your application utilizes the filter list in order to gain maximum pushdown benefits. The `where` string may be more intuitive for users writing queries during testing, but it will not have the performance benefits of the filter list in a production environment. From 504090fbbb006466e6b86338b037fce454fc2b0d Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 11:35:29 +0100 Subject: [PATCH 25/33] Update website/docs/docs/cloud/cloud-cli-installation.md --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 5ce10b08355..3de2bbc694b 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -27,7 +27,7 @@ The dbt Cloud CLI is available in all [deployment regions](/docs/cloud/about-clo - Ensure you are using dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-core-in-cloud) to upgrade. - Avoid using SSH tunneling for [Postgres and Redshift](/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb) connections. -- Avoid using [PrivateLink](/cloud/secure/about-privatelink). +- Avoid using [PrivateLink](/docs/cloud/secure/about-privatelink). ## Install dbt Cloud CLI From 69c13e39fb1908edbf91aa77cebdf6b9fdc83153 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 25 Oct 2023 11:46:29 +0100 Subject: [PATCH 26/33] remove callout --- .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md index b8041a5d197..6cc32a4c836 100644 --- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md +++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md @@ -5,10 +5,6 @@ description: Learn about partner integration guidelines, roadmap, and connectivi --- -import NewChanges from '/snippets/_new-sl-changes.md'; - - - To fit your tool within the world of the Semantic Layer, dbt Labs offers some best practice recommendations for how to expose metrics and allow users to interact with them seamlessly. :::note From 6897f67edbc93e2297877533a2a6e4dc391e3c36 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 25 Oct 2023 13:17:58 +0100 Subject: [PATCH 27/33] turn to cards per PM --- .../avail-sl-integrations.md | 6 - website/snippets/_sl-partner-links.md | 43 +- website/static/img/icons/delphi.svg | 550 ++++++++++++++++++ website/static/img/icons/push.svg | 49 ++ website/static/img/icons/white/delphi.svg | 550 ++++++++++++++++++ website/static/img/icons/white/push.svg | 49 ++ 6 files changed, 1234 insertions(+), 13 deletions(-) create mode 100644 website/static/img/icons/delphi.svg create mode 100644 website/static/img/icons/push.svg create mode 100644 website/static/img/icons/white/delphi.svg create mode 100644 website/static/img/icons/white/push.svg diff --git a/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md b/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md index fb0136e29d8..22178a14b5b 100644 --- a/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md +++ b/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md @@ -20,12 +20,6 @@ import AvailIntegrations from '/snippets/_sl-partner-links.md'; -## Other integrations - -You can also integrate the following tools with the dbt Semantic Layer: -- [Push.ai](https://docs.push.ai/semantic-layer-integrations/dbt-semantic-layer) -- [Delphi](delphihq.com) - ### Custom integration - You can create custom integrations using different languages and tools. We support connecting with JDBC, ADBC, and GraphQL APIs. For more info, check out [our examples on GitHub](https://github.com/dbt-labs/example-semantic-layer-clients/). diff --git a/website/snippets/_sl-partner-links.md b/website/snippets/_sl-partner-links.md index ce2087bf380..435d5dc2773 100644 --- a/website/snippets/_sl-partner-links.md +++ b/website/snippets/_sl-partner-links.md @@ -1,6 +1,8 @@ The following tools integrate with the dbt Semantic Layer: -
+ + +
+ icon="google-sheets-logo-icon"/> -

+ +
+ + + + +
+ +

Before you connect to these tools, you'll need to first [set up the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and [generate a service token](/docs/dbt-cloud-apis/service-tokens) to create **Semantic Layer Only** and **Metadata Only** permissions. diff --git a/website/static/img/icons/delphi.svg b/website/static/img/icons/delphi.svg new file mode 100644 index 00000000000..a154b7dfa82 --- /dev/null +++ b/website/static/img/icons/delphi.svg @@ -0,0 +1,550 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/website/static/img/icons/push.svg b/website/static/img/icons/push.svg new file mode 100644 index 00000000000..8693b207f58 --- /dev/null +++ b/website/static/img/icons/push.svg @@ -0,0 +1,49 @@ + +Created with Fabric.js 3.5.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/website/static/img/icons/white/delphi.svg b/website/static/img/icons/white/delphi.svg new file mode 100644 index 00000000000..8d767499ab9 --- /dev/null +++ b/website/static/img/icons/white/delphi.svg @@ -0,0 +1,550 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/website/static/img/icons/white/push.svg b/website/static/img/icons/white/push.svg new file mode 100644 index 00000000000..05cd660607e --- /dev/null +++ b/website/static/img/icons/white/push.svg @@ -0,0 +1,49 @@ + +Created with Fabric.js 3.5.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From eb4f00c65fb0f6df22bd2725c902b953303deec0 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 17:02:51 +0100 Subject: [PATCH 28/33] Update tableau.md --- website/docs/docs/use-dbt-semantic-layer/tableau.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/tableau.md b/website/docs/docs/use-dbt-semantic-layer/tableau.md index 2eba9d0c318..5ac3858c766 100644 --- a/website/docs/docs/use-dbt-semantic-layer/tableau.md +++ b/website/docs/docs/use-dbt-semantic-layer/tableau.md @@ -10,14 +10,16 @@ The Tableau integration with the dbt Semantic Layer is a [beta feature](/docs/db ::: -The Tableau integration allows you to use worksheets to query the Semantic Layer directly and produce your dashboards with trusted data. This integration provides a live connection to the dbt Semantic Layer through Tableau Desktop. +The Tableau integration allows you to use worksheets to query the Semantic Layer directly and produce your dashboards with trusted data. + +This integration provides a live connection to the dbt Semantic Layer through Tableau Desktop. (Tableau Cloud or Tableau Server is not supported for this integration). ## Prerequisites 1. You must have [Tableau Desktop](https://www.tableau.com/en-gb/products/desktop) installed 2. Authenticate in Tableau Desktop (you can authenticate with a license, or credentials used to login to Tableau Server or Online) 3. You need your dbt Cloud host, [Environment ID](/docs/use-dbt-semantic-layer/setup-sl#set-up-dbt-semantic-layer) and [service token](/docs/dbt-cloud-apis/service-tokens) to log in. This account should be set up with the dbt Semantic Layer. -4. You must a dbt Cloud Team or Enterprise [account](https://www.getdbt.com/pricing) and multi-tenant [deployment](/docs/cloud/about-cloud/regions-ip-addresses). (Single-Tenant coming soon) +4. You must have a dbt Cloud Team or Enterprise [account](https://www.getdbt.com/pricing) and multi-tenant [deployment](/docs/cloud/about-cloud/regions-ip-addresses). (Single-Tenant coming soon) ## Installing @@ -38,7 +40,7 @@ The Tableau integration allows you to use worksheets to query the Semantic Layer Once you authenticate, the system will direct you to the data source page with all the metrics and dimensions configured in your Semantic Layer. -- From there, go directly to a worksheet in the bottom left hand corner. +- From there, go directly to a worksheet in the bottom left-hand corner. - Then, you'll find all the metrics and dimensions that are available to query on the left-hand side of your window. Visit the [Tableau documentation](https://help.tableau.com/current/pro/desktop/en-us/gettingstarted_overview.htm) to learn more about how to use Tableau worksheets and dashboards. From a7c5ab83c4f4681ddfa790b6d366f4f1a0d560b5 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 17:07:03 +0100 Subject: [PATCH 29/33] Update website/docs/docs/use-dbt-semantic-layer/tableau.md --- website/docs/docs/use-dbt-semantic-layer/tableau.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/tableau.md b/website/docs/docs/use-dbt-semantic-layer/tableau.md index 5ac3858c766..b7fd6c87f24 100644 --- a/website/docs/docs/use-dbt-semantic-layer/tableau.md +++ b/website/docs/docs/use-dbt-semantic-layer/tableau.md @@ -17,7 +17,7 @@ This integration provides a live connection to the dbt Semantic Layer through Ta ## Prerequisites 1. You must have [Tableau Desktop](https://www.tableau.com/en-gb/products/desktop) installed -2. Authenticate in Tableau Desktop (you can authenticate with a license, or credentials used to login to Tableau Server or Online) +2. Log in to Tableau Desktop using either your license or the login details you use for Tableau Server or Tableau Online. 3. You need your dbt Cloud host, [Environment ID](/docs/use-dbt-semantic-layer/setup-sl#set-up-dbt-semantic-layer) and [service token](/docs/dbt-cloud-apis/service-tokens) to log in. This account should be set up with the dbt Semantic Layer. 4. You must have a dbt Cloud Team or Enterprise [account](https://www.getdbt.com/pricing) and multi-tenant [deployment](/docs/cloud/about-cloud/regions-ip-addresses). (Single-Tenant coming soon) From e2abbfdf4aa801a319a8403228370a4b0f373be1 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 17:07:47 +0100 Subject: [PATCH 30/33] Update website/docs/docs/use-dbt-semantic-layer/tableau.md --- website/docs/docs/use-dbt-semantic-layer/tableau.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/tableau.md b/website/docs/docs/use-dbt-semantic-layer/tableau.md index b7fd6c87f24..9bc32ec3622 100644 --- a/website/docs/docs/use-dbt-semantic-layer/tableau.md +++ b/website/docs/docs/use-dbt-semantic-layer/tableau.md @@ -12,7 +12,7 @@ The Tableau integration with the dbt Semantic Layer is a [beta feature](/docs/db The Tableau integration allows you to use worksheets to query the Semantic Layer directly and produce your dashboards with trusted data. -This integration provides a live connection to the dbt Semantic Layer through Tableau Desktop. (Tableau Cloud or Tableau Server is not supported for this integration). +This integration provides a live connection to the dbt Semantic Layer through Tableau Desktop. ## Prerequisites From 26e4a494f26ea8cad03df18a75b4e1ec6b1d897c Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 17:17:54 +0100 Subject: [PATCH 31/33] Update sl-jdbc.md creating pr to move roxi's changes to this repo, going to merge without separate approval as I've approved this pr in the internal repo already --- website/docs/docs/dbt-cloud-apis/sl-jdbc.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/docs/docs/dbt-cloud-apis/sl-jdbc.md b/website/docs/docs/dbt-cloud-apis/sl-jdbc.md index 4d0d4f6d1a2..e10d057dc75 100644 --- a/website/docs/docs/dbt-cloud-apis/sl-jdbc.md +++ b/website/docs/docs/dbt-cloud-apis/sl-jdbc.md @@ -254,14 +254,14 @@ Where filters in API allow for a filter list or string. We recommend using the f Where Filters have a few objects that you can use: -- `Dimension()` - This is used for any categorical or time dimensions. If used for a time dimension, granularity is required - `Dimension('metric_time').grain('week')` or `Dimension('customer__country')` +- `Dimension()` - Used for any categorical or time dimensions. If used for a time dimension, granularity is required - `Dimension('metric_time').grain('week')` or `Dimension('customer__country')` - `Entity()` - Used for entities like primary and foreign keys - `Entity('order_id')` Note: If you prefer a more explicit path to create the `where` clause, you can optionally use the `TimeDimension` feature. This helps separate out categorical dimensions from time-related ones. The `TimeDimesion` input takes the time dimension name and also requires granularity, like this: `TimeDimension('metric_time', 'MONTH')`. -Use the following example to query using a `where` filter with the string format: +- Use the following example to query using a `where` filter with the string format: ```bash select * from {{ @@ -271,13 +271,13 @@ where="{{ Dimension('metric_time').grain('month') }} >= '2017-03-09' AND {{ Dim }} ``` -Use the following example to query using a `where` filter with a filter list format: +- (Recommended for better performance) Use the following example to query using a `where` filter with a filter list format: ```bash select * from {{ semantic_layer.query(metrics=['food_order_amount', 'order_gross_profit'], group_by=[Dimension('metric_time').grain('month'),'customer__customer_type'], -where=[{{ Dimension('metric_time').grain('month') }} >= '2017-03-09', {{ Dimension('customer__customer_type' }} in ('new'), {{ Entity('order_id') }} = 10]) +where=["{{ Dimension('metric_time').grain('month') }} >= '2017-03-09'", "{{ Dimension('customer__customer_type' }} in ('new')", "{{ Entity('order_id') }} = 10"] }} ``` From 49cc7875336c6397e2573c0d765e9dbc12b7b0bc Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 25 Oct 2023 17:36:26 +0100 Subject: [PATCH 32/33] Update cloud-cli-installation.md remove link typo --- website/docs/docs/cloud/cloud-cli-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index 3de2bbc694b..179af745685 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -19,7 +19,7 @@ dbt commands are run against dbt Cloud's infrastructure and benefit from: * [Automatic deferral](/docs/cloud/about-cloud-develop-defer) of build artifacts to your Cloud project's production environment. * Speedier, lower-cost builds. * Support for dbt Mesh ([cross-project `ref`](/docs/collaborate/govern/project-dependencies)), -https://github.com/dbt-labs/docs.getdbt.com/pull/4320* Significant platform improvements, to be released over the coming months. +* Significant platform improvements, to be released over the coming months. ## Prerequisites From 9de47f8533d81836ebdfc42f49f9260bbad15417 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 25 Oct 2023 14:02:13 -0400 Subject: [PATCH 33/33] Update website/docs/docs/cloud/manage-access/set-up-sso-okta.md --- website/docs/docs/cloud/manage-access/set-up-sso-okta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/manage-access/set-up-sso-okta.md b/website/docs/docs/cloud/manage-access/set-up-sso-okta.md index cae592d2827..4079cc488c4 100644 --- a/website/docs/docs/cloud/manage-access/set-up-sso-okta.md +++ b/website/docs/docs/cloud/manage-access/set-up-sso-okta.md @@ -171,7 +171,7 @@ configured in the steps above. | **Log in with** | Okta | | **Identity Provider SSO Url** | Paste the **Identity Provider Single Sign-On URL** shown in the Okta setup instructions | | **Identity Provider Issuer** | Paste the **Identity Provider Issuer** shown in the Okta setup instructions | -| **X.509 Certificate** | Paste the **X.509 Certificate** shown in the Okta setup instructions; **Note:** When the certificate expires, an Okta admin will have to generate a new one to be pasted into dbt Cloud for uninterrupted application access | +| **X.509 Certificate** | Paste the **X.509 Certificate** shown in the Okta setup instructions;
**Note:** When the certificate expires, an Okta admin will have to generate a new one to be pasted into dbt Cloud for uninterrupted application access. | | **Slug** | Enter your desired login slug. Users will be able to log into dbt Cloud by navigating to `https://YOUR_ACCESS_URL/enterprise-login/LOGIN-SLUG`, replacing `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan. Login slugs must be unique across all dbt Cloud accounts, so pick a slug that uniquely identifies your company. |