Merge branch 'current' into aug-sl-rn

website/blog/2022-04-14-add-ci-cd-to-bitbucket.md

@@ -10,6 +10,8 @@ hide_table_of_contents: false
 
 date: 2022-05-06
 is_featured: true
+keywords:
+  - dbt core pipeline, slim ci pipeline, slim cd pipeline, bitbucket
 ---
 
 

website/dbt-versions.js

@@ -10,16 +10,14 @@
  * @property {string} EOLDate "End of Life" date which is used to show the EOL banner
  * @property {boolean} isPrerelease Boolean used for showing the prerelease banner
  * @property {string} customDisplay Allows setting a custom display name for the current version
+ * 
+ * customDisplay for dbt Cloud should be a version ahead of latest dbt Core release (GA or beta).
  */
 exports.versions = [
   {
     version: "1.9.1",
     customDisplay: "Cloud (Versionless)",
   },
-  {
-    version: "1.9",
-    isPrerelease: true,
-  },
   {
     version: "1.8",
     EOLDate: "2025-04-15",

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-7-semantic-structure.md

@@ -20,6 +20,10 @@ The first thing you need to establish is how you’re going to consistently stru
 
 It’s not terribly difficult to shift between these (it can be done with some relatively straightforward shell scripting), and this is purely a decision based on your developers’ preference (i.e. it has no impact on execution or performance), so don’t feel locked in to either path. Just pick the one that feels right and you can always shift down the road if you change your mind.
 
+:::tip 
+Make sure to save all semantic models and metrics under the directory defined in the [`model-paths`](/reference/project-configs/model-paths) (or a subdirectory of it, like `models/semantic_models/`). If you save them outside of this path, it will result in an empty `semantic_manifest.json` file, and your semantic models or metrics won't be recognized.
+:::
+
 ## Naming
 
 Next, establish your system for consistent file naming:

website/docs/docs/build/hooks-operations.md

@@ -72,6 +72,41 @@ You can use hooks to provide database-specific functionality not available out-o
 
 You can also use a [macro](/docs/build/jinja-macros#macros) to bundle up hook logic. Check out some of the examples in the reference sections for [on-run-start and on-run-end hooks](/reference/project-configs/on-run-start-on-run-end) and [pre- and post-hooks](/reference/resource-configs/pre-hook-post-hook).
 
+<File name='models/<model_name>.sql'>
+
+```sql
+{{ config(
+    pre_hook=[
+      "{{ some_macro() }}"
+    ]
+) }}
+```
+
+</File>
+
+<File name='models/properties.yml'>
+
+```yaml
+models:
+  - name: <model_name>
+    config:
+      pre_hook:
+        - "{{ some_macro() }}"
+```
+
+</File>
+
+<File name='dbt_project.yml'>
+
+```yaml
+models:
+  <project_name>:
+    +pre-hook:
+      - "{{ some_macro() }}"
+```
+
+</File>
+
 ## About operations
 
 Operations are [macros](/docs/build/jinja-macros#macros) that you can run using the [`run-operation`](/reference/commands/run-operation) command. As such, operations aren't actually a separate resource in your dbt project — they are just a convenient way to invoke a macro without needing to run a model.

website/docs/docs/build/jinja-macros.md

@@ -74,7 +74,7 @@ group by 1
 You can recognize Jinja based on the delimiters the language uses, which we refer to as "curlies":
 - **Expressions `{{ ... }}`**: Expressions are used when you want to output a string. You can use expressions to reference [variables](/reference/dbt-jinja-functions/var) and call [macros](/docs/build/jinja-macros#macros).
 - **Statements `{% ... %}`**: Statements don't output a string. They are used for control flow, for example, to set up `for` loops and `if` statements, to [set](https://jinja.palletsprojects.com/en/3.1.x/templates/#assignments) or [modify](https://jinja.palletsprojects.com/en/3.1.x/templates/#expression-statement) variables, or to define macros.
--  **Comments `{# ... #}`**: Jinja comments are used to prevent the text within the comment from executing or outputing a string.
+-  **Comments `{# ... #}`**: Jinja comments are used to prevent the text within the comment from executing or outputing a string. Don't use `--` for comment.
 
 When used in a dbt model, your Jinja needs to compile to a valid query. To check what SQL your Jinja compiles to:
 * **Using dbt Cloud:** Click the compile button to see the compiled SQL in the Compiled SQL pane

website/docs/docs/cloud/about-cloud/browsers.md

@@ -27,4 +27,4 @@ To improve your experience using dbt Cloud, we suggest that you turn off ad bloc
 
 A session is a period of time during which you’re signed in to a dbt Cloud account from a browser. If you close your browser, it will end your session and log you out. You'll need to log in again the next time you try to access dbt Cloud. 
 
-If you've logged in using [SSO](/docs/cloud/manage-access/sso-overview) or [OAuth](/docs/cloud/git/connect-github#personally-authenticate-with-github), you can customize your maximum session duration, which might vary depending on your identity provider (IdP).
+If you've logged in using [SSO](/docs/cloud/manage-access/sso-overview), you can customize your maximum session duration, which might vary depending on your identity provider (IdP).

website/docs/docs/cloud/git/connect-github.md

@@ -7,7 +7,6 @@ sidebar_label: "Connect to GitHub"
 
 
 Connecting your GitHub account to dbt Cloud provides convenience and another layer of security to dbt Cloud:
-- Log into dbt Cloud using OAuth through GitHub.
 - Import new GitHub repositories with a couple clicks during dbt Cloud project setup.
 - Clone repos using HTTPS rather than SSH.
 - Trigger [Continuous integration](/docs/deploy/continuous-integration)(CI) builds when pull requests are opened in GitHub.
@@ -48,15 +47,15 @@ To connect your dbt Cloud account to your GitHub account:
    - Read and write access to Workflows
 
 6. Once you grant access to the app, you will be redirected back to dbt Cloud and shown a linked account success state. You are now personally authenticated. 
-7. Ask your team members to [personally authenticate](/docs/cloud/git/connect-github#personally-authenticate-with-github) by connecting their GitHub profiles.
+7. Ask your team members to individually authenticate by connecting their [personal GitHub profiles](#authenticate-your-personal-github-account).
 
 ## Limiting repository access in GitHub
 If you are your GitHub organization owner, you can also configure the dbt Cloud GitHub application to have access to only select repositories. This configuration must be done in GitHub, but we provide an easy link in dbt Cloud to start this process.
 <Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/connecting-github/configure-github.png" title="Configuring the dbt Cloud app"/>
 
-## Personally authenticate with GitHub
+## Authenticate your personal GitHub account
 
-Once the dbt Cloud admin has [set up a connection](/docs/cloud/git/connect-github#installing-dbt-cloud-in-your-github-account) to your organization GitHub account, you need to personally authenticate, which improves the security of dbt Cloud by enabling you to log in using OAuth through GitHub.
+After the dbt Cloud administrator [sets up a connection](/docs/cloud/git/connect-github#installing-dbt-cloud-in-your-github-account) to your organization's GitHub account, you need to authenticate using your personal account. You must connect your personal GitHub profile to dbt Cloud to use the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud) and [CLI](/docs/cloud/cloud-cli-installation) and verify your read and write access to the repository.
 
 :::info GitHub profile connection
 
@@ -77,7 +76,7 @@ To connect a personal GitHub account:
 
 4. Once you approve authorization, you will be redirected to dbt Cloud, and you should now see your connected account. 
 
-The next time you log into dbt Cloud, you will be able to do so via OAuth through GitHub, and if you're on the Enterprise plan, you're ready to use the dbt Cloud IDE or dbt Cloud CLI.
+You can now use the dbt Cloud IDE or dbt Cloud CLI.
 
 
 ## FAQs

website/docs/docs/cloud/manage-access/set-up-snowflake-oauth.md

@@ -43,7 +43,7 @@ CREATE OR REPLACE SECURITY INTEGRATION DBT_CLOUD
   ENABLED = TRUE
   OAUTH_CLIENT = CUSTOM
   OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
-  OAUTH_REDIRECT_URI = LOCATED_REDIRECT_URI
+  OAUTH_REDIRECT_URI = 'LOCATED_REDIRECT_URI'
   OAUTH_ISSUE_REFRESH_TOKENS = TRUE
   OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;
 ```

website/docs/docs/cloud/secure/ip-restrictions.md

@@ -13,7 +13,7 @@ import SetUpPages from '/snippets/_available-tiers-iprestrictions.md';
 
 IP Restrictions help control which IP addresses are allowed to connect to dbt Cloud. IP restrictions allow dbt Cloud customers to meet security and compliance controls by only allowing approved IPs to connect to their dbt Cloud environment. This feature is supported in all regions across NA, Europe, and Asia-Pacific, but contact us if you have questions about availability.
 
-## Configuring IP Restrictions
+## Configuring IP restrictions
 
 To configure IP restrictions, go to **Account Settings** → **IP Restrictions**. IP restrictions provide two methods for determining which IPs can access dbt Cloud: an allowlist and a blocklist. IPs in the allowlist are allowed to access dbt Cloud, and IPs in the deny list will be blocked from accessing dbt Cloud. IP Restrictions can be used for a range of use cases, including:
 
@@ -29,7 +29,7 @@ For any version control system integrations (Github, Gitlab, ADO, etc.) inbound
 
 To add an IP to the allowlist, from the **IP Restrictions** page:
 
-1.  Click **edit**
+1.  Click **Edit**
 2. Click **Add Rule**
 3. Add name and description for the rule
     - For example, Corporate VPN CIDR Range
@@ -39,7 +39,9 @@ To add an IP to the allowlist, from the **IP Restrictions** page:
 	- You can add multiple ranges in the same rule.
 6. Click **Save**
 
-Note that simply adding the IP Ranges will not enforce IP restrictions. For more information, see the section “Enabling Restrictions.”
+Add multiple IP ranges by clicking the **Add IP range** button to create a new text field.
+
+Note that simply adding the IP Ranges will not enforce IP restrictions. For more information, see the [Enabling restrictions](#enabling-restrictions) section.
 
 If you only want to allow the IP ranges added to this list and deny all other requests, adding a denylist is not necessary. By default, if only an allow list is added, dbt Cloud will only allow IPs in the allowable range and deny all other IPs. However, you can add a denylist if you want to deny specific IP addresses within your allowlist CIDR range.
 
@@ -65,9 +67,9 @@ It is possible to put an IP range on one list and then a sub-range or IP address
 
 :::
 
-## Enabling Restrictions
+## Enabling restrictions
 
-Once you are done adding all your ranges, IP restrictions can be enabled by selecting the **Enable IP restrictions** button and clicking **Save**. If your IP address is in any of the denylist ranges, you won’t be able to save or enable IP restrictions - this is done to prevent accidental account lockouts. If you do get locked out due to IP changes on your end, please reach out to support@dbtlabs.com
+Once you are done adding all your ranges, IP restrictions can be enabled by selecting the **Enable IP restrictions** button and clicking **Save**. If your IP address is in any of the denylist ranges, you won’t be able to save or enable IP restrictions - this is done to prevent accidental account lockouts. If you do get locked out due to IP changes on your end, please reach out to support@getdbt.com
 
 Once enabled, when someone attempts to access dbt Cloud from a restricted IP, they will encounter one of the following messages depending on whether they use email & password or SSO login. 
 

website/docs/docs/collaborate/data-tile.md

@@ -9,16 +9,20 @@ image: /img/docs/collaborate/dbt-explorer/data-tile-pass.jpg
 # Embed data health tile in dashboards <Lifecycle status='beta' />
 
 With data health tiles, stakeholders will get an at-a-glance confirmation on whether the data they’re looking at is stale or degraded. This trust signal allows teams to immediately go back into Explorer to see more details and investigate issues.
+
 :::info Available in beta
 Data health tile is currently available in open beta.
 :::
+
 The data health tile:
 
 - Distills trust signals for data consumers.
 - Deep links you into dbt Explorer where you can further dive into upstream data issues.
 - Provides richer information and makes it easier to debug.
 - Revamps the existing, [job-based tiles](#job-based-data-health).
 
+Data health tiles rely on [exposures](/docs/build/exposures) to surface trust signals in your dashboards. When you configure exposures in your dbt project, you are explicitly defining how specific outputs—like dashboards or reports—depend on your data models.
+
 <Lightbox src="/img/docs/collaborate/dbt-explorer/data-tiles.png" width="60%" title="Embed data health tiles in your dashboards to distill trust signals for data consumers." />
 
 ## Prerequisites
@@ -34,43 +38,45 @@ First, be sure to enable [source freshness](/docs/deploy/source-freshness) in
 
 1. Navigate to dbt Explorer by clicking on the **Explore** link in the navigation.
 2. In the main **Overview** page, go to the left navigation.
-3. Under the **Resources** tab, click on **Exposures** to view the exposures list.
+3. Under the **Resources** tab, click on **Exposures** to view the [exposures](/docs/build/exposures) list.
 4. Select a dashboard exposure and go to the **General** tab to view the data health information.
-5. In this tab, you’ll see: 
-   - Data health status: Data freshness passed, Data quality passed, Data may be stale, Data quality degraded
-   - Name of the exposure.
+5. In this tab, you’ll see:   
+   - Name of the exposure. 
+   - Data health status: Data freshness passed, Data quality passed, Data may be stale, Data quality degraded.
    - Resource type (model, source, and so on).
    - Dashboard status: Failure, Pass, Stale.
    - You can also see the last check completed, the last check time, and the last check duration.
-6. You can also click the **Open Dashboard** button on the upper right to immediately view this in your analytics tool.
+6. You can click the **Open Dashboard** button on the upper right to immediately view this in your analytics tool.
 
 <Lightbox src="/img/docs/collaborate/dbt-explorer/data-tile-exposures.jpg" width="95%" title="View an exposure in dbt Explorer." />
 
 ## Embed in your dashboard
 
-Once you’ve navigated to the auto-exposure in dbt Explorer, you’ll need to set up your dashboard status tile and [service token](/docs/dbt-cloud-apis/service-tokens):
+Once you’ve navigated to the auto-exposure in dbt Explorer, you’ll need to set up your data health tile and [service token](/docs/dbt-cloud-apis/service-tokens). You can embed data health tile to any analytics tool that supports URL or iFrame embedding.
+
+Follow these steps to set up your data health tile:
 
 1. Go to **Account settings** in dbt Cloud.
 2. Select **API tokens** in the left sidebar and then **Service tokens**.
 3. Click on **Create service token** and give it a name.
-4. Select the [**Metadata Only** permission](/docs/dbt-cloud-apis/service-tokens). This token will be used to embed the exposure tile in your dashboard in the later steps.
+4. Select the [**Metadata Only**](/docs/dbt-cloud-apis/service-tokens) permission. This token will be used to embed the tile in your dashboard in the later steps.
 <Lightbox src="/img/docs/collaborate/dbt-explorer/data-tile-setup.jpg" width="95%" title="Set up your dashboard status tile and service token to embed a data health tile" />
 
-5. Copy the **Metadata Only token** and save it in a secure location. You'll need it token in the next steps.
+5. Copy the **Metadata Only** token and save it in a secure location. You'll need it token in the next steps.
 6. Navigate back to dbt Explorer and select an exposure.
 7. Below the **Data health** section, expand on the toggle for instructions on how to embed the exposure tile (if you're an account admin with develop permissions). 
 8. In the expanded toggle, you'll see a text field where you can paste your **Metadata Only token**.
 <Lightbox src="/img/docs/collaborate/dbt-explorer/data-tile-example.jpg" width="85%" title="Expand the toggle to embded data health tile into your dashboard." />
 
-9. Once you’ve pasted your token, you can select either **URL** or **iFrame** depending on which you need to install into your dashboard.
+9. Once you’ve pasted your token, you can select either **URL** or **iFrame** depending on which you need to add to your dashboard.
 
 If your analytics tool supports iFrames, you can embed the dashboard tile within it. 
 
-### Embed data health tile in Tableau
-To embed the data health tile in Tableau, follow these steps:
+#### Tableau example
+Here’s an example with Tableau, where you can embed the iFrame in a web page object:
 
-1. Ensure you've copied the embed iFrame content in dbt Explorer.
-2. For the revamped environment-based exposure tile you can insert these fields into the following iFrame, and then embed them with your dashboard. This is the iFrame that is available from the **Exposure details** page in dbt Explorer.
+- Ensure you've copied the embed iFrame snippet from the dbt Explorer **Data health** section.
+- **For the revamped environment-based exposure tile** &mdash; Insert the following fields into the following iFrame. Then embed them with your dashboard. This is the iFrame available from the **Exposure details** page in dbt Explorer.
 
     `<iframe src='https://metadata.YOUR_ACCESS_URL/exposure-tile?uniqueId=<exposure_unique_id>&environmentType=production&environmentId=<environment_id>&token=<metadata_token>' />`
 
@@ -82,7 +88,7 @@ To embed the data health tile in Tableau, follow these steps:
 <Lightbox src="/img/docs/collaborate/dbt-explorer/data-tile-stale.jpg" width="60%" title="Example of stale of degraded Data health tile in your dashboard." />
 </DocCarousel>
 
-3. For the job-based exposure tile you can insert these three fields into the following iFrame, and then embed them with your dashboard. The next section will have more details on the job-based exposure tile.
+- **For job-based exposure tile** &mdash; Insert the following fields into the following iFrame. Then embed them with your dashboard. The next [section](#job-based-data-health) will have more details on the job-based exposure tile.
 
     `<iframe src='https://metadata.YOUR_ACCESS_URL/exposure-tile?name=<exposure_name>&environment_id=<environment_id>&token=<metadata_token>' />`