diff --git a/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-6-advanced-metrics.md b/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-6-advanced-metrics.md index e5c6e452dac..66523ab7efa 100644 --- a/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-6-advanced-metrics.md +++ b/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-6-advanced-metrics.md @@ -21,13 +21,11 @@ We're not limited to just passing measures through to our metrics, we can also _ ```YAML - name: food_revenue - description: The revenue from food in each order. - label: Food Revenue - type: simple - type_params: - measure: revenue - filter: | - {{ Dimension('order__is_food_order') }} = true + description: The revenue from food in each order. + label: Food Revenue + type: simple + type_params: + measure: food_revenue ``` - 📝 Now we can set up our ratio metric. diff --git a/website/docs/best-practices/how-we-style/1-how-we-style-our-dbt-models.md b/website/docs/best-practices/how-we-style/1-how-we-style-our-dbt-models.md index 0157af63cfb..bf8924807a0 100644 --- a/website/docs/best-practices/how-we-style/1-how-we-style-our-dbt-models.md +++ b/website/docs/best-practices/how-we-style/1-how-we-style-our-dbt-models.md @@ -8,6 +8,10 @@ id: 1-how-we-style-our-dbt-models - 👥 Models should be pluralized, for example, `customers`, `orders`, `products`. - 🔑 Each model should have a primary key. - 🔑 The primary key of a model should be named `_id`, for example, `account_id`. This makes it easier to know what `id` is being referenced in downstream joined models. +- Use underscores for naming dbt models; avoid dots. + - ✅ `models_without_dots` + - ❌ `models.with.dots` + - Most data platforms use dots to separate `database.schema.object`, so using underscores instead of dots reduces your need for [quoting](/reference/resource-properties/quoting) as well as the risk of issues in certain parts of dbt Cloud. For more background, refer to [this GitHub issue](https://github.com/dbt-labs/dbt-core/issues/3246). - 🔑 Keys should be string data types. - 🔑 Consistency is key! Use the same field names across models where possible. For example, a key to the `customers` table should be named `customer_id` rather than `user_id` or 'id'. - ❌ Do not use abbreviations or aliases. Emphasize readability over brevity. For example, do not use `cust` for `customer` or `o` for `orders`. diff --git a/website/docs/docs/build/models.md b/website/docs/docs/build/models.md index 1cf2fbafeda..fa2a002a3ef 100644 --- a/website/docs/docs/build/models.md +++ b/website/docs/docs/build/models.md @@ -6,8 +6,6 @@ pagination_next: "docs/build/sql-models" pagination_prev: null --- -## Overview - dbt Core and Cloud are composed of different moving parts working harmoniously. All of them are important to what dbt does — transforming data—the 'T' in ELT. When you execute `dbt run`, you are running a model that will transform your data without that data ever leaving your warehouse. Models are where your developers spend most of their time within a dbt environment. Models are primarily written as a `select` statement and saved as a `.sql` file. While the definition is straightforward, the complexity of the execution will vary from environment to environment. Models will be written and rewritten as needs evolve and your organization finds new ways to maximize efficiency. diff --git a/website/docs/docs/build/sql-models.md b/website/docs/docs/build/sql-models.md index a0dd174278b..d0dc8becdcb 100644 --- a/website/docs/docs/build/sql-models.md +++ b/website/docs/docs/build/sql-models.md @@ -29,7 +29,10 @@ dbt's Python capabilities are an extension of its capabilities with SQL models. A SQL model is a `select` statement. Models are defined in `.sql` files (typically in your `models` directory): - Each `.sql` file contains one model / `select` statement - The model name is inherited from the filename. -- Models can be nested in subdirectories within the `models` directory +- We strongly recommend using underscores for model names, not dots. For example, use `models/my_model.sql` instead of `models/my.model.sql`. +- Models can be nested in subdirectories within the `models` directory. + +Refer to [How we style our dbt models](/best-practices/how-we-style/1-how-we-style-our-dbt-models) for details on how we recommend you name your models. When you execute the [`dbt run` command](/reference/commands/run), dbt will build this model by wrapping it in a `create view as` or `create table as` statement. diff --git a/website/docs/docs/cloud/dbt-cloud-ide/develop-in-the-cloud.md b/website/docs/docs/cloud/dbt-cloud-ide/develop-in-the-cloud.md index 57146ec513a..0d87a790042 100644 --- a/website/docs/docs/cloud/dbt-cloud-ide/develop-in-the-cloud.md +++ b/website/docs/docs/cloud/dbt-cloud-ide/develop-in-the-cloud.md @@ -133,38 +133,32 @@ The dbt Cloud IDE makes it possible to [build and view](/docs/collaborate/build- ## Related docs -- [dbt Cloud features](/docs/cloud/about-cloud/dbt-cloud-features) -- [IDE user interface](/docs/cloud/dbt-cloud-ide/ide-user-interface) +- [How we style our dbt projects](/best-practices/how-we-style/0-how-we-style-our-dbt-projects) +- [User interface](/docs/cloud/dbt-cloud-ide/ide-user-interface) - [Version control basics](/docs/collaborate/git/version-control-basics) - [dbt Commands](/reference/dbt-commands) -- [dbt Cloud IDE release notes](/tags/ide) ## Related questions -
- -
- Is there a cost to using the Cloud IDE? -
-
Not at all! You can use dbt Cloud when you sign up for the Free Developer plan, which comes with one developer seat. If you’d like to access more features or have more developer seats, you can upgrade your account to the Team or Enterprise plan. See dbt pricing plans for more details.
-
-
-
- Can I be a contributor to dbt Cloud? -
-
Anyone can contribute to the dbt project. And whether it's a dbt package, a plugin, dbt-core, or this documentation site, contributing to the open-source code that supports the dbt ecosystem is a great way to level yourself up as a developer, and give back to the community. See Contributing for details on what to expect when contributing to the dbt open source software (OSS).
-
-
-
- What is the difference between developing on the dbt Cloud IDE, the dbt Cloud CLI, and dbt Core? -
-
You can develop dbt using the web-based IDE in dbt Cloud or on the command line interface using the dbt Cloud CLI or open-source dbt Core, all of which enable you to execute dbt commands. The key distinction between the dbt Cloud CLI and dbt Core is the dbt Cloud CLI is tailored for dbt Cloud's infrastructure and integrates with all its features.

- — - dbt Cloud IDE: dbt Cloud is a web-based application that allows you to develop dbt projects with the IDE, includes a purpose-built scheduler, and provides an easier way to share your dbt documentation with your team. The IDE is a faster and more reliable way to deploy your dbt models and provides a real-time editing and execution environment for your dbt project.

- — - dbt Cloud CLI: The dbt Cloud CLI allows you to run dbt commands against your dbt Cloud development environment from your local command line or code editor. It supports cross-project ref, speedier, lower-cost builds, automatic deferral of build artifacts, and more.

- — - dbt Core: dbt Core is an open-sourced software that’s freely available. You can build your dbt project in a code editor, and run dbt commands from the command line. -
-
-
+ + + +Not at all! You can use dbt Cloud when you sign up for the Free Developer plan, which comes with one developer seat. If you’d like to access more features or have more developer seats, you can upgrade your account to the Team or Enterprise plan.
+ +Refer to dbt pricing plans for more details. + + + +As a proprietary product, dbt Cloud's source code isn't available for community contributions. If you want to build something in the dbt ecosystem, we encourage you to review [this article](/community/contributing/contributing-coding) about contributing to a dbt package, a plugin, dbt-core, or this documentation site. Participation in open-source is a great way to level yourself up as a developer, and give back to the community. + + + +You can develop dbt using the web-based IDE in dbt Cloud or on the command line interface using the dbt Cloud CLI or open-source dbt Core, all of which enable you to execute dbt commands. The key distinction between the dbt Cloud CLI and dbt Core is the dbt Cloud CLI is tailored for dbt Cloud's infrastructure and integrates with all its features: + +- dbt Cloud IDE: dbt Cloud is a web-based application that allows you to develop dbt projects with the IDE, includes a purpose-built scheduler, and provides an easier way to share your dbt documentation with your team. The IDE is a faster and more reliable way to deploy your dbt models and provides a real-time editing and execution environment for your dbt project. + +- dbt Cloud CLI: The dbt Cloud CLI allows you to run dbt commands against your dbt Cloud development environment from your local command line or code editor. It supports cross-project ref, speedier, lower-cost builds, automatic deferral of build artifacts, and more. + +- dbt Core: dbt Core is an open-sourced software that’s freely available. You can build your dbt project in a code editor, and run dbt commands from the command line + + diff --git a/website/docs/docs/cloud/migration.md b/website/docs/docs/cloud/migration.md index 0c43a287bbe..8604976738f 100644 --- a/website/docs/docs/cloud/migration.md +++ b/website/docs/docs/cloud/migration.md @@ -33,7 +33,7 @@ If your account is scheduled for migration, you will see a banner indicating you 3. **IDE sessions** — Any uncommitted changes in the IDE might be lost during the migration process. dbt Labs _strongly_ encourages you to commit all changes in the IDE before your scheduled migration time. 4. **User invitations** — Any pending user invitations will be invalidated during the migration. You can resend the invitations once the migration is complete. -5. **Git integrations** — Integrations with GitHub, GitLab, and Azure DevOps will need to be manually updated. dbt Labs will not be migrating any accounts using these integrations at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration. +5. **Git integrations** — Native integrations with [GitLab](/docs/cloud/git/connect-gitlab#for-the-dbt-cloud-enterprise-tier) and [Azure DevOps](/docs/cloud/git/connect-azure-devops) will need to be manually updated. dbt Labs will not be migrating any accounts using these integrations at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration. 6. **SSO integrations** — Integrations with SSO identity providers (IdPs) will need to be manually updated. dbt Labs will not be migrating any accounts using SSO at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration. ## Post-migration @@ -42,4 +42,4 @@ After migration, if you completed all the [Pre-migration checklist](#pre-migrati You have the option to log in to dbt Cloud at a different URL: * If you were previously logging in at `cloud.getdbt.com`, you should instead plan to login at `us1.dbt.com`. The original URL will still work, but you’ll have to click through to be redirected upon login. - * You may also log in directly with your account’s unique [access URL](https://next.docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses#accessing-your-account). \ No newline at end of file + * You may also log in directly with your account’s unique [access URL](https://next.docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses#accessing-your-account). diff --git a/website/docs/docs/cloud/secure/postgres-privatelink.md b/website/docs/docs/cloud/secure/postgres-privatelink.md index ef07d15c128..d34efb17ca1 100644 --- a/website/docs/docs/cloud/secure/postgres-privatelink.md +++ b/website/docs/docs/cloud/secure/postgres-privatelink.md @@ -49,13 +49,13 @@ On the provisioned VPC endpoint service, click the **Allow principals** tab. Cli - Principal: `arn:aws:iam::346425330055:role/MTPL_Admin` - + ### 3. Obtain VPC Endpoint Service Name Once the VPC Endpoint Service is provisioned, you can find the service name in the AWS console by navigating to **VPC** → **Endpoint Services** and selecting the appropriate endpoint service. You can copy the service name field value and include it in your communication to dbt Cloud support. - + ### 4. Add the required information to the template below, and submit your request to [dbt Support](https://docs.getdbt.com/community/resources/getting-help#dbt-cloud-support): ``` @@ -68,6 +68,12 @@ Subject: New Multi-Tenant PrivateLink Request dbt Labs will work on your behalf to complete the PrivateLink setup. Please allow 1-2 business days for this process to complete. Support will contact you when the endpoint is available. +### 5. Accepting the connection request + +When you have been notified that the resources are provisioned within the dbt Cloud environment, you must accept the endpoint connection (unless the VPC Endpoint Service is set to auto-accept connection requests). Requests can be accepted through the AWS console, as seen below, or through the AWS CLI. + + + ## Create Connection in dbt Cloud Once dbt Cloud support completes the configuration, you can start creating new connections using PrivateLink. diff --git a/website/docs/docs/cloud/secure/redshift-privatelink.md b/website/docs/docs/cloud/secure/redshift-privatelink.md index c42c703556b..d727ba5796c 100644 --- a/website/docs/docs/cloud/secure/redshift-privatelink.md +++ b/website/docs/docs/cloud/secure/redshift-privatelink.md @@ -85,13 +85,13 @@ On the provisioned VPC endpoint service, click the **Allow principals** tab. Cli - Principal: `arn:aws:iam::346425330055:role/MTPL_Admin` - + ### 3. Obtain VPC Endpoint Service Name Once the VPC Endpoint Service is provisioned, you can find the service name in the AWS console by navigating to **VPC** → **Endpoint Services** and selecting the appropriate endpoint service. You can copy the service name field value and include it in your communication to dbt Cloud support. - + ### 4. Add the required information to the template below, and submit your request to [dbt Support](https://docs.getdbt.com/community/resources/getting-help#dbt-cloud-support): ``` diff --git a/website/docs/docs/cloud/secure/vcs-privatelink.md b/website/docs/docs/cloud/secure/vcs-privatelink.md index 13bb97dd6cd..41c61d20e2d 100644 --- a/website/docs/docs/cloud/secure/vcs-privatelink.md +++ b/website/docs/docs/cloud/secure/vcs-privatelink.md @@ -23,8 +23,11 @@ Creating an Interface VPC PrivateLink connection requires creating multiple AWS This approach is distinct from and does not require you to implement VPC peering between your AWS account(s) and dbt Cloud. -You need these resource to create a PrivateLink connection, which allows the dbt Cloud application to connect to your self-hosted cloud VCS. These resources can be created via the AWS Console, AWS CLI, or Infrastructure-as-Code such as [Terraform](https://registry.terraform.io/providers/hashicorp/aws/latest/docs) or [AWS CloudFormation](https://aws.amazon.com/cloudformation/). +### 1. Provision AWS resources +Creating an Interface VPC PrivateLink connection requires creating multiple AWS resources in the account containing, or connected to, your self-hosted cloud VCS. These resources can be created via the AWS Console, AWS CLI, or Infrastructure-as-Code such as [Terraform](https://registry.terraform.io/providers/hashicorp/aws/latest/docs) or [AWS CloudFormation](https://aws.amazon.com/cloudformation/). + +- **Security Group (AWS hosted only)** — If you are connecting to an existing VCS install, this likely already exists, however, you may need to add or modify Security Group rules to accept traffic from the Network Load Balancer (NLB) created for this Endpoint Service. - **Target Group(s)** - A [Target Group](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html) is attached to a [Listener](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-listeners.html) on the NLB and is responsible for routing incoming requests to healthy targets in the group. If connecting to the VCS system over both SSH and HTTPS, two **Target Groups** will need to be created. - **Target Type (choose most applicable):** - **Instance/ASG:** Select existing EC2 instance(s) where the VCS system is running, or [an autoscaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/attach-load-balancer-asg.html) (ASG) to automatically attach any instances launched from that ASG. @@ -46,23 +49,43 @@ You need these resource to create a PrivateLink connection, which allows the dbt - **Load balancer:** Attach the NLB created in the previous step. - **Acceptance required (recommended)**: When enabled, requires a new connection request to the VPC Endpoint Service to be accepted by the customer before connectivity is allowed ([details](https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#accept-reject-connection-requests)). - Once these resources have been provisioned, access needs to be granted for the dbt Labs AWS account to create a VPC Endpoint in our VPC. On the newly created VPC Endpoint Service, add a new [Allowed Principal](https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#add-remove-permissions) for the appropriate dbt Labs principal: +### 2. Grant dbt AWS account access to the VPC Endpoint Service - - **AWS Account ID:** `arn:aws:iam:::root` (contact your dbt Labs account representative for appropriate account ID). +Once these resources have been provisioned, access needs to be granted for the dbt Labs AWS account to create a VPC Endpoint in our VPC. On the provisioned VPC endpoint service, click the **Allow principals** tab. Click **Allow principals** to grant access. Enter the ARN of the following IAM role in the appropriate production AWS account and save your changes ([details](https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#add-remove-permissions)). -### Completing the connection + - Principal: `arn:aws:iam::346425330055:role/MTPL_Admin` -To complete the connection, dbt Labs must now provision a VPC Endpoint to connect to your VPC Endpoint Service. This requires you send the following information: - - - VPC Endpoint Service name: + - +### 3. Obtain VPC Endpoint Service Name - - **DNS configuration:** If the connection to the VCS service requires a custom domain and/or URL for TLS, a private hosted zone can be configured by the dbt Labs Infrastructure team in the dbt Cloud private network. For example: - - **Private hosted zone:** `examplecorp.com` - - **DNS record:** `github.examplecorp.com` +Once the VPC Endpoint Service is provisioned and configured find the service name in the AWS console by navigating to **VPC** → **Endpoint Services** and selecting the appropriate endpoint service. Copy the service name field value and include it in your communication to dbt Cloud support. -### Accepting the connection request + + +:::note Custom DNS configuration + +If the connection to the VCS service requires a custom domain and/or URL for TLS, a private hosted zone can be configured by the dbt Labs Infrastructure team in the dbt Cloud private network. For example: + - Private hosted zone: examplecorp.com + - DNS record: github.examplecorp.com + +::: + +### 4. Add the required information to the template below, and submit your request to [dbt Support](https://docs.getdbt.com/community/resources/getting-help#dbt-cloud-support): +``` +Subject: New Multi-Tenant PrivateLink Request +- Type: VCS Interface-type +- VPC Endpoint Service Name: +- Custom DNS (optional) + - Private hosted zone: + - DNS record: +- VCS install AWS Region (e.g., us-east-1, eu-west-2): +- dbt Cloud multi-tenant environment (US, EMEA, AU): +``` + +dbt Labs will work on your behalf to complete the PrivateLink setup. Please allow 1-2 business days for this process to complete. Support will contact you when the endpoint is available. + +### 5. Accepting the connection request When you have been notified that the resources are provisioned within the dbt Cloud environment, you must accept the endpoint connection (unless the VPC Endpoint Service is set to auto-accept connection requests). Requests can be accepted through the AWS console, as seen below, or through the AWS CLI. @@ -73,10 +96,11 @@ Once you accept the endpoint connection request, you can use the PrivateLink end ## Configure in dbt Cloud Once dbt confirms that the PrivateLink integration is complete, you can use it in a new or existing git configuration. + 1. Select **PrivateLink Endpoint** as the connection type, and your configured integrations will appear in the dropdown menu. 2. Select the configured endpoint from the drop down list. 3. Click **Save**. - \ No newline at end of file + diff --git a/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md b/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md index 8efb1ec0d37..68e829b310a 100644 --- a/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md +++ b/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md @@ -7,7 +7,7 @@ With the Discovery API, you can query the metadata in dbt Cloud to learn more ab You can use the API in a variety of ways to get answers to your business questions. Below describes some of the uses of the API and is meant to give you an idea of the questions this API can help you answer. -| Use Case | Outcome | Example Questions | +| Use case | Outcome |
Example questions
| | --- | --- | --- | | [Performance](#performance) | Identify inefficiencies in pipeline execution to reduce infrastructure costs and improve timeliness. |
  • What’s the latest status of each model?
  • Do I need to run this model?
  • How long did my DAG take to run?
| | [Quality](#quality) | Monitor data source freshness and test results to resolve issues and drive trust in data. |
  • How fresh are my data sources?
  • Which tests and models failed?
  • What’s my project’s test coverage?
| diff --git a/website/docs/faqs/Accounts/transfer-account.md b/website/docs/faqs/Accounts/transfer-account.md index d82dfbf505a..c848547f808 100644 --- a/website/docs/faqs/Accounts/transfer-account.md +++ b/website/docs/faqs/Accounts/transfer-account.md @@ -10,7 +10,7 @@ You can transfer your dbt Cloud [access control](/docs/cloud/manage-access/about | Account plan| Steps | | ------ | ---------- | -| **Developer** | You can transfer ownership by changing the email directly on your dbt Cloud profile page, which you can access using this URL when you replace `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan: `https://YOUR_ACCESS_URL/settings/profile` | +| **Developer** | You can transfer ownership by changing the email directly on your dbt Cloud profile page, which you can access using this URL when you replace `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan: `https://YOUR_ACCESS_URL/settings/profile`. Before doing this, please ensure that you unlink your GitHub profile. | | **Team** | Existing account admins with account access can add users to, or remove users from the owner group. | | **Enterprise** | Account admins can add users to, or remove users from a group with Account Admin permissions. | | **If all account owners left the company** | If the account owner has left your organization, you will need to work with _your_ IT department to have incoming emails forwarded to the new account owner. Once your IT department has redirected the emails, you can request to reset the user password. Once you log in, you can change the email on the Profile page when you replace `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan: `https://YOUR_ACCESS_URL/settings/profile`. | @@ -19,3 +19,5 @@ When you make any account owner and email changes: - The new email address _must_ be verified through our email verification process. - You can update any billing email address or [Notifications Settings](/docs/deploy/job-notifications) to reflect the new account owner changes, if applicable. +- When transferring account ownership, please ensure you [unlink](/faqs/Accounts/git-account-in-use) your GitHub account in dbt Cloud. This is because you can only have your Git account linked to one dbt Cloud user account. + diff --git a/website/docs/reference/resource-configs/where.md b/website/docs/reference/resource-configs/where.md index fe83c22847d..63c40b99902 100644 --- a/website/docs/reference/resource-configs/where.md +++ b/website/docs/reference/resource-configs/where.md @@ -122,7 +122,7 @@ tests: The rendering context for the `where` config is the same as for all configurations defined in `.yml` files. You have access to `{{ var() }}` and `{{ env_var() }}`, but you **do not** have access to custom macros for setting this config. If you do want to use custom macros to template out the `where` filter for certain tests, there is a workaround. -As of v0.21, dbt defines a [`get_where_subquery` macro](https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/adapters/include/global_project/macros/materializations/tests/where_subquery.sql). +As of v0.21, dbt defines a [`get_where_subquery` macro](https://github.com/dbt-labs/dbt-adapters/blob/main/dbt/include/global_project/macros/materializations/tests/where_subquery.sql). dbt replaces `{{ model }}` in generic test definitions with `{{ get_where_subquery(relation) }}`, where `relation` is a `ref()` or `source()` for the resource being tested. The default implementation of this macro returns: - `{{ relation }}` when the `where` config is not defined (`ref()` or `source()`) diff --git a/website/docs/reference/resource-properties/description.md b/website/docs/reference/resource-properties/description.md index f8469dc3494..fee1d50aaf3 100644 --- a/website/docs/reference/resource-properties/description.md +++ b/website/docs/reference/resource-properties/description.md @@ -157,7 +157,7 @@ A user-defined description. Can be used to document: - analyses, and analysis columns - macros, and macro arguments -These descriptions are used in the documentation website rendered by dbt (see [the documentation guide](/docs/collaborate/documentation)). +These descriptions are used in the documentation website rendered by dbt (refer to [the documentation guide](/docs/collaborate/documentation) or [dbt Explorer](/docs/collaborate/explore-projects)). Descriptions can include markdown, as well as the [`doc` jinja function](/reference/dbt-jinja-functions/doc). @@ -265,7 +265,7 @@ Orders can be one of the following statuses: | status | description | |----------------|---------------------------------------------------------------------------| | placed | The order has been placed but has not yet left the warehouse | -| shipped | The order has ben shipped to the customer and is currently in transit | +| shipped | The order has been shipped to the customer and is currently in transit | | completed | The order has been received by the customer | | returned | The order has been returned by the customer and received at the warehouse | @@ -305,7 +305,13 @@ models: ### Include an image from your repo in your descriptions -To include an image from your repository in your descriptions: + +This section applies to dbt Core users only. Including an image from your repository ensures your images are version-controlled. + +Both dbt Cloud and dbt Core users can [include an image from the web](#include-an-image-from-the-web-in-your-descriptions), which offers dynamic content, reduced repository size, accessibility, and ease of collaboration. + +To include an image in your model's `description` field: + 1. Add the file in a subdirectory, e.g. `assets/dbt-logo.svg` 2. Set the [`asset-paths` config](/reference/project-configs/asset-paths) in your `dbt_project.yml` file so that this directory gets copied to the `target/` directory as part of `dbt docs generate` @@ -336,19 +342,17 @@ models: -_[CLI users only]_ - 3. Run `dbt docs generate` — the `assets` directory will be copied to the `target` directory 4. Run `dbt docs serve` — the image will be rendered as part of your project documentation: - - -If mixing images and text together, also consider using a docs block. +If mixing images and text, also consider using a docs block. ### Include an image from the web in your descriptions -Use the image URL to render the image. +This section applies to dbt Cloud and dbt Core users. Including an image from the web offers dynamic content, reduced repository size, accessibility, and ease of collaboration. + +To include images from the web, specify the image URL in your model's `description` field: @@ -367,5 +371,5 @@ models: -If mixing images and text together, also consider using a docs block. +If mixing images and text, also consider using a docs block. diff --git a/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/vpc-endpoint-service-name.png b/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/vpc-endpoint-service-name.png deleted file mode 100644 index 9dc5e070cdd..00000000000 Binary files a/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/vpc-endpoint-service-name.png and /dev/null differ diff --git a/website/static/img/docs/dbt-cloud/privatelink-allow-principals.png b/website/static/img/docs/dbt-cloud/privatelink-allow-principals.png new file mode 100644 index 00000000000..13e3197adcd Binary files /dev/null and b/website/static/img/docs/dbt-cloud/privatelink-allow-principals.png differ diff --git a/website/static/img/docs/dbt-cloud/privatelink-endpoint-service-name.png b/website/static/img/docs/dbt-cloud/privatelink-endpoint-service-name.png new file mode 100644 index 00000000000..0b7c0236947 Binary files /dev/null and b/website/static/img/docs/dbt-cloud/privatelink-endpoint-service-name.png differ diff --git a/website/static/img/docs/dbt-cloud/redshiftprivatelink5.png b/website/static/img/docs/dbt-cloud/redshiftprivatelink5.png deleted file mode 100644 index 138df761da1..00000000000 Binary files a/website/static/img/docs/dbt-cloud/redshiftprivatelink5.png and /dev/null differ diff --git a/website/static/img/docs/dbt-cloud/redshiftprivatelink6.png b/website/static/img/docs/dbt-cloud/redshiftprivatelink6.png deleted file mode 100644 index 3d80d7ae1cc..00000000000 Binary files a/website/static/img/docs/dbt-cloud/redshiftprivatelink6.png and /dev/null differ