Merge branch 'current' into nfiann-ci-and-git

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

@@ -3,14 +3,14 @@ title: "Dremio setup"
 description: "Read this guide to learn about the Dremio warehouse setup in dbt."
 meta:
   maintained_by: Dremio
-  authors: 'Dremio (formerly Fabrice Etanchaud)'
+  authors: 'Dremio'
   github_repo: 'dremio/dbt-dremio'
   pypi_package: 'dbt-dremio'
-  min_core_version: 'v1.2.0'
+  min_core_version: 'v1.8.0'
   cloud_support: Not Supported
   min_supported_version: 'Dremio 22.0'
-  slack_channel_name: 'n/a'
-  slack_channel_link: 'https://www.getdbt.com/community'
+  slack_channel_name: 'db-dremio'
+  slack_channel_link: '[https://www.getdbt.com/community](https://getdbt.slack.com/archives/C049G61TKBK)'
   platform_name: 'Dremio'
   config_page: '/reference/resource-configs/no-configs'
 ---
@@ -36,10 +36,6 @@ Before connecting from project to Dremio Cloud, follow these prerequisite steps:
 
 * Ensure that you are using version 22.0 or later.
 * Ensure that Python 3.9.x or later is installed on the system that you are running dbt on.
-* Enable these support keys in your Dremio cluster:
-  * `dremio.iceberg.enabled`
-  * `dremio.iceberg.ctas.enabled`
-  * `dremio.execution.support_unlimited_splits`
 
   See <a target="_blank" rel="noopener noreferrer" href="https://docs.dremio.com/software/advanced-administration/support-settings/#support-keys">Support Keys</a> in the Dremio documentation for the steps.
 * If you want to use TLS to secure the connection between dbt and Dremio Software, configure full wire encryption in your Dremio cluster. For instructions, see <a target="_blank" rel="noopener noreferrer" href="https://docs.dremio.com/software/deployment/wire-encryption-config/">Configuring Wire Encryption</a>.
@@ -84,7 +80,7 @@ For descriptions of the configurations in these profiles, see [Configurations](#
 [project name]:
   outputs:
     dev:
-      cloud_host: https://api.dremio.cloud
+      cloud_host: api.dremio.cloud
       cloud_project_id: [project ID]
       object_storage_source: [name]
       object_storage_path: [path]
@@ -161,7 +157,7 @@ For descriptions of the configurations in these profiles, see [Configurations](#
 
 | Configuration | Required? | Default Value | Description |
 | --- | --- | --- | --- |
-| `cloud_host` | Yes | `https://api.dremio.cloud` | US Control Plane: `https://api.dremio.cloud`<br></br>EU Control Plane: `https://api.eu.dremio.cloud` |
+| `cloud_host` | Yes | `api.dremio.cloud` | US Control Plane: `api.dremio.cloud`<br></br>EU Control Plane: `api.eu.dremio.cloud` |
 | `user` | Yes | None | Email address used as a username in Dremio Cloud | 
 | `pat` | Yes | None | The personal access token to use for authentication. See [Personal Access Tokens](https://docs.dremio.com/cloud/security/authentication/personal-access-token/) for instructions about obtaining a token. | 
 | `cloud_project_id` | Yes | None | The ID of the Sonar project in which to run transformations. | 

website/docs/docs/deploy/ci-jobs.md

@@ -190,6 +190,20 @@ To validate _all_ semantic nodes in your project, add the following command to d
 
 <FAQ path="Troubleshooting/gitlab-webhook"/>
 
+<DetailsToggle alt_header="CI jobs aren't triggering occasionally when opening a PR using the Azure DevOps (ADO) integration">
+
+dbt Cloud won't trigger a CI job run if the latest commit in a pull or merge request has already triggered a run for that job. However, some providers (like GitHub) will enforce the result of the existing run on multiple pull/merge requests.
+
+Scenarios where dbt Cloud does not trigger a CI job with Azure DevOps:
+
+1. Reusing a branch in a new PR
+   - If you abandon a previous PR (PR 1) that triggered a CI job for the same branch (`feature-123`) merging into `main`, and then open a new PR (PR 2) with the same branch merging into`main` &mdash; dbt Cloud won't trigger a new CI job for PR 2.
+
+2. Reusing the same commit
+   - If you create a new PR (PR 2) on the same commit (`#4818ceb`) as a previous PR (PR 1) that triggered a CI job &mdash; dbt Cloud won't trigger a new CI job for PR 2.
+
+</DetailsToggle>
+
 <DetailsToggle alt_header="Temporary schemas aren't dropping">
 If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates one of these issues:
 - You have overridden the <code>generate_schema_name</code> macro and it isn't using <code>dbt_cloud_pr_</code> as the prefix.