Merge branch 'current' into glue_is_trusted

.github/pull_request_template.md

@@ -12,7 +12,8 @@ Uncomment if you're publishing docs for a prerelease version of dbt (delete if n
 - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
 - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
 -->
-- [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines.
+- [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines.
+- [ ] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
 - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
 
 Adding new pages (delete if not applicable):
@@ -22,4 +23,4 @@ Adding new pages (delete if not applicable):
 Removing or renaming existing pages (delete if not applicable):
 - [ ] Remove page from `website/sidebars.js`
 - [ ] Add an entry `website/static/_redirects`
-- [ ] [Ran link testing](https://github.com/dbt-labs/docs.getdbt.com#running-the-cypress-tests-locally) to update the links that point to the deleted page
+- [ ] Run link testing locally with `npm run build` to update the links that point to the deleted page

.github/workflows/asana-connection.yml

@@ -0,0 +1,17 @@
+name: Show PR Status in Asana
+on:
+  pull_request:
+    types: [opened, reopened]
+
+jobs:
+  create-asana-attachment-job:
+    runs-on: ubuntu-latest
+    name: Create pull request attachments on Asana tasks
+    steps:
+      - name: Create pull request attachments
+        uses: Asana/create-app-attachment-github-action@latest
+        id: postAttachment
+        with:
+          asana-secret: ${{ secrets.ASANA_SECRET }}
+      - name: Log output status
+        run: echo "Status is ${{ steps.postAttachment.outputs.status }}"

website/docs/docs/build/measures.md

@@ -6,19 +6,13 @@ sidebar_label: "Measures"
 tags: [Metrics, Semantic Layer]
 ---
 
-Measures are aggregations performed on columns in your model. They can be used as final metrics or serve as building blocks for more complex metrics. Measures have several inputs, which are described in the following table along with their field types.
-
-| Parameter | Description | Type |
-| --------- | ----------- | ---- |
-| [`name`](#name) | Provide a name for the measure, which must be unique and can't be repeated across all semantic models in your dbt project. | Required |
-| [`description`](#description) | Describes the calculated measure. | Optional |
-| [`agg`](#aggregation) | dbt supports aggregations such as `sum`, `min`, `max`, and more. Refer to [Aggregation](/docs/build/measures#aggregation) for the full list of supported aggregation types. | Required |
-| [`expr`](#expr) | You can either reference an existing column in the table or use a SQL expression to create or derive a new one. | Optional |
-| [`non_additive_dimension`](#non-additive-dimensions) | Non-additive dimensions can be specified for measures that cannot be aggregated over certain dimensions, such as bank account balances, to avoid producing incorrect results. | Optional |
-| `agg_params` | specific aggregation properties such as a percentile. | Optional |
-| `agg_time_dimension` | The time field. Defaults to the default agg time dimension for the semantic model.  | Optional |
-| `label` | How the metric appears in project docs and downstream integrations. | Required |
+Measures are aggregations performed on columns in your model. They can be used as final metrics or serve as building blocks for more complex metrics. 
 
+Measures have several inputs, which are described in the following table along with their field types.
+
+import MeasuresParameters from '/snippets/_sl-measures-parameters.md';
+
+<MeasuresParameters />
 
 ## Measure spec
 

website/docs/docs/build/semantic-models.md

@@ -40,17 +40,17 @@ The complete spec for semantic models is below:
 
 ```yaml
 semantic_models:
-  - name: the_name_of_the_semantic_model  ## Required
-    description: same as always           ## Optional
-    model: ref('some_model')              ## Required
-    defaults:                             ## Required
-      agg_time_dimension: dimension_name  ## Required if the model contains dimensions
-    entities:                             ## Required
-      - see more information in entities
-    measures:                             ## Optional
-      - see more information in measures section
-    dimensions:                           ## Required
-      - see more information in dimensions section
+  - name: the_name_of_the_semantic_model      ## Required
+    description: same as always               ## Optional
+    model: ref('some_model')                  ## Required
+    default:                                  ## Required
+      agg_time_dimension: dimension_name    ## Required if the model contains dimensions
+    entities:                                 ## Required
+       - see more information in entities
+    measures:                                 ## Optional
+       - see more information in measures section
+    dimensions:                               ## Required
+       - see more information in dimensions section
     primary_entity: >-
       if the semantic model has no primary entity, then this property is required. #Optional if a primary entity exists, otherwise Required
 ```
@@ -230,16 +230,14 @@ For semantic models with a measure, you must have a [primary time group](/docs/b
 
 ### Measures
 
-[Measures](/docs/build/measures) are aggregations applied to columns in your data model. They can be used as the foundational building blocks for more complex metrics, or be the final metric itself. Measures have various parameters which are listed in a table along with their descriptions and types.
+[Measures](/docs/build/measures) are aggregations applied to columns in your data model. They can be used as the foundational building blocks for more complex metrics, or be the final metric itself. 
+
+Measures have various parameters which are listed in a table along with their descriptions and types.
+
+import MeasuresParameters from '/snippets/_sl-measures-parameters.md';
+
+<MeasuresParameters />
 
-| Parameter | Description | Field type |
-| --- | --- | --- |
-| `name`| Provide a name for the measure, which must be unique and can't be repeated across all semantic models in your dbt project. | Required |
-| `description` | Describes the calculated measure. | Optional |
-| `agg` | dbt supports the following aggregations: `sum`, `max`, `min`, `count_distinct`, and `sum_boolean`. | Required |
-| `expr` | You can either reference an existing column in the table or use a SQL expression to create or derive a new one. | Optional |
-| `non_additive_dimension` | Non-additive dimensions can be specified for measures that cannot be aggregated over certain dimensions, such as bank account balances, to avoid producing incorrect results. | Optional |
-| `create_metric` | You can create a metric directly from a measure with `create_metric: True` and specify its display name with create_metric_display_name. Default is false. | Optional |
 
 
 import SetUpPages from '/snippets/_metrics-dependencies.md';

website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md

@@ -13,10 +13,12 @@ The following fields are required when creating a Postgres, Redshift, or AlloyDB
 | Port | Usually 5432 (Postgres) or 5439 (Redshift) | `5439` |
 | Database | The logical database to connect to and run queries against. | `analytics` |
 
-**Note**: When you set up a Redshift or Postgres connection in dbt Cloud, SSL-related parameters aren't available as inputs.
+**Note**: When you set up a Redshift or Postgres connection in dbt Cloud, SSL-related parameters aren't available as inputs. 
 
 <Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/postgres-redshift-connection.png" width="70%" title="Configuring a Redshift connection"/>
 
+For dbt Cloud users, please log in using the default Database username and password. Note this is because [`IAM` authentication](https://docs.aws.amazon.com/redshift/latest/mgmt/generating-user-credentials.html) is not compatible with dbt Cloud.
+
 ### Connecting via an SSH Tunnel
 
 To connect to a Postgres, Redshift, or AlloyDB instance via an SSH tunnel, select the **Use SSH Tunnel** option when creating your connection. When configuring the tunnel, you must supply the hostname, username, and port for the [bastion server](#about-the-bastion-server-in-aws).

website/docs/docs/collaborate/govern/model-contracts.md

@@ -125,8 +125,8 @@ Select the adapter-specific tab for more information on [constraint](/reference/
 | Constraint type | Support       | Platform enforcement |
 |:-----------------|:-------------|:---------------------|
 | not_null        | ✅ Supported  | ✅ Enforced     |
-| primary_key     | ✅ Supported  | ✅ Enforced     |
-| foreign_key     | ✅ Supported  | ✅ Enforced     |
+| primary_key     | ✅ Supported  | ❌ Not enforced     |
+| foreign_key     | ✅ Supported  | ❌ Not enforced     |
 | unique          | ❌ Not supported | ❌ Not enforced |
 | check           | ❌ Not supported | ❌ Not enforced |
 

website/docs/docs/core/connect-data-platform/redshift-setup.md

@@ -70,8 +70,9 @@ pip is the easiest way to install the adapter:
 The authentication methods that dbt Core supports are: 
 
 - `database` — Password-based authentication (default, will be used if `method` is not provided)
-- `IAM` — IAM 
+- `IAM` — IAM
 
+For dbt Cloud users, log in using the default **Database username** and **password**. This is necessary because dbt Cloud does not support `IAM` authentication.
 
 Click on one of these authentication methods for further details on how to configure your connection profile. Each tab also includes an example `profiles.yml` configuration file for you to review.
 

website/docs/docs/core/connect-data-platform/teradata-setup.md

@@ -61,6 +61,7 @@ pip is the easiest way to install the adapter:
 | dbt-teradata |  dbt-core  | dbt-teradata-util |  dbt-util      |
 |--------------|------------|-------------------|----------------|
 | 1.2.x        | 1.2.x      | 0.1.0             | 0.9.x or below |
+| 1.6.7        | 1.6.7      | 1.1.1             | 1.1.1          |
 
 
 <h2> Configuring {frontMatter.meta.pypi_package} </h2>

website/docs/docs/dbt-cloud-apis/project-state.md

@@ -66,7 +66,7 @@ Most Discovery API use cases will favor the _applied state_ since it pertains to
 | Seed      | Yes              | Yes                  | Yes                | Downstream            | Applied & definition |
 | Snapshot  | Yes              | Yes                  | Yes                | Upstream & downstream | Applied & definition |
 | Test      | Yes              | Yes                  | No                 | Upstream              | Applied & definition |
-| Exposure  | No               | No                   | No                 | Upstream              | Applied & definition |
+| Exposure  | No               | No                   | No                 | Upstream              | Definition 	  |
 | Metric    | No               | No                   | No                 | Upstream & downstream | Definition           |
 | Semantic model | No          | No                   | No                 | Upstream & downstream | Definition           |
 | Group     | No               | No                   | No                 | Downstream            | Definition           |