Merge branch 'current' into clickable-lifecycle

website/blog/authors.yml

@@ -137,7 +137,7 @@ colin_rogers:
   organization: dbt Labs
 dave_connors:
   image_url: /img/blog/authors/dconnors.jpeg
-  job_title: Senior Developer Experience Advocate
+  job_title: Staff Developer Experience Advocate
   links:
     - icon: fa-github
       url: https://github.com/dave-connors-3

website/docs/best-practices/best-practice-workflows.md

@@ -188,15 +188,8 @@ where created_at >= dateadd('day', -3, current_date)
 {% endif %}
 ```
 
-### Use hooks to manage privileges on objects that dbt creates
-Use `grant` statements from [hooks](/docs/build/hooks-operations) to ensure that permissions are applied to the objects created by dbt. By codifying these grant statements in hooks, you can version control and repeatably apply these permissions.
-
-
-:::info Recommended grant statements
-
-We've shared the exact grant statements we use over on [Discourse](https://discourse.getdbt.com/t/the-exact-grant-statements-we-use-in-a-dbt-project/430)
-
-:::
+### Use grants to manage privileges on objects that dbt creates
+Use `grants` in [resource configs](/reference/resource-configs/grants) to ensure that permissions are applied to the objects created by dbt. By codifying these grant statements, you can version control and repeatably apply these permissions.
 
 ### Separate source-centric and business-centric transformations
 When modeling data, we frequently find there are two stages:
@@ -208,3 +201,6 @@ We find it most useful to separate these two types of transformations into diffe
 
 ### Managing whitespace generated by Jinja
 If you're using macros or other pieces of Jinja in your models, your compiled SQL (found in the `target/compiled` directory) may contain unwanted whitespace. Check out the [Jinja documentation](http://jinja.pocoo.org/docs/2.10/templates/#whitespace-control) to learn how to control generated whitespace.
+
+## Related docs
+- [Updating our permissioning guidelines: grants as configs in dbt Core v1.2](https://docs.getdbt.com/blog/configuring-grants)

website/docs/docs/build/incremental-microbatch.md

@@ -310,11 +310,9 @@ For example, if you have a microbatch model with 12 batches, you can execute tho
 
 To enable parallel execution, you must:
 
-- Use a supported adapter:
-  - Snowflake
-  - Databricks
+- Use Snowflake as a supported adapter.
   - More adapters coming soon!
-    - We'll be continuing to test and add concurrency support for adapters. This means that some adapters might get concurrency support _after_ the 1.9 initial release.
+  - We'll be continuing to test and add concurrency support for adapters. This means that some adapters might get concurrency support _after_ the 1.9 release.
 
 - Meet [additional conditions](#how-parallel-batch-execution-works) described in the following section.
 

website/docs/docs/build/snapshots.md

@@ -46,7 +46,7 @@ This order is now in the "shipped" state, but we've lost the information about w
 
 <VersionBlock firstVersion="1.9">
 
-Configure your snapshots in YAML files to tell dbt how to detect record changes. Define snapshots configurations in YAML files, alongside your models, for a cleaner, faster, and more consistent set up. 
+Configure your snapshots in YAML files to tell dbt how to detect record changes. Define snapshots configurations in YAML files, alongside your models, for a cleaner, faster, and more consistent set up. Place snapshot YAML files in the models directory or in a snapshots directory. 
 
 <File name='snapshots/orders_snapshot.yml'>
 

website/docs/docs/cloud/cloud-cli-installation.md

@@ -313,16 +313,10 @@ This alias will allow you to use the <code>dbt-cloud</code> command to invoke th
 
 </DetailsToggle>
 
-<DetailsToggle alt_header="Why am I receiving a `Session occupied` error?">
-
-
-If you've ran a dbt command and receive a <code>Session occupied</code> error, you can reattach to your existing session with <code>dbt reattach</code> and then press <code>Control-C</code> and choose to cancel the invocation.
-
-</DetailsToggle>
-
 <DetailsToggle alt_header="Why am I receiving a `Stuck session` error when trying to run a new command?">
 
+The dbt Cloud CLI allows only one command that writes to the data warehouse at a time. If you attempt to run multiple write commands simultaneously (for example, `dbt run` and `dbt build`), you will encounter a `stuck session` error. To resolve this, cancel the specific invocation by passing its ID to the cancel command. For more information, refer to [parallel execution](/reference/dbt-commands#parallel-execution).
 
-The Cloud CLI allows only one command that writes to the data warehouse at a time. If you attempt to run multiple write commands simultaneously (for example, `dbt run` and `dbt build`), you will encounter a `stuck session` error. To resolve this, cancel the specific invocation by passing its ID to the cancel command. For more information, refer to [parallel execution](/reference/dbt-commands#parallel-execution).
+</DetailsToggle>
 
-</DetailsToggle>
+<FAQ path="Troubleshooting/long-sessions-cloud-cli" />

website/docs/docs/cloud/configure-cloud-cli.md

@@ -124,7 +124,7 @@ As a tip, most command-line tools have a `--help` flag to show available command
 - `dbt run --help`: Lists the flags available for the `run` command
 :::
 
-### Lint SQL files 
+## Lint SQL files 
 
 From the dbt Cloud CLI, you can invoke [SQLFluff](https://sqlfluff.com/) which is a modular and configurable SQL linter that warns you of complex functions, syntax, formatting, and compilation errors. Many of the same flags that you can pass to SQLFluff are available from the dbt Cloud CLI.
 
@@ -154,7 +154,8 @@ When running `dbt sqlfluff` from the dbt Cloud CLI, the following are important
 - An SQLFluff command will return an exit code of 0 if it ran with any file violations. This dbt behavior differs from SQLFluff behavior, where a linting violation returns a non-zero exit code. dbt Labs plans on addressing this in a later release.
 
 ## FAQs
-<Expandable alt_header="How to create a .dbt directory and move your file">
+
+<DetailsToggle alt_header="How to create a .dbt directory and move your file">
 
 If you've never had a `.dbt` directory, you should perform the following recommended steps to create one. If you already have a `.dbt` directory, move the `dbt_cloud.yml` file into it.
 
@@ -195,11 +196,12 @@ move %USERPROFILE%\Downloads\dbt_cloud.yml %USERPROFILE%\.dbt\dbt_cloud.yml
 
 This command moves the `dbt_cloud.yml` from the `Downloads` folder to the `.dbt` folder. If your `dbt_cloud.yml` file is located elsewhere, adjust the path accordingly.
 
-</Expandable>
+</DetailsToggle>
 
-<Expandable alt_header="How to skip artifacts from being downloaded">
+<DetailsToggle alt_header="How to skip artifacts from being downloaded">
 
 By default, [all artifacts](/reference/artifacts/dbt-artifacts) are downloaded when you execute dbt commands from the dbt Cloud CLI. To skip these files from being downloaded, add `--download-artifacts=false` to the command you want to run. This can help improve run-time performance but might break workflows that depend on assets like the [manifest](/reference/artifacts/manifest-json). 
 
+</DetailsToggle>
 
-</Expandable>
+<FAQ path="Troubleshooting/long-sessions-cloud-cli" />

website/docs/docs/cloud/git/connect-azure-devops.md

@@ -1,7 +1,7 @@
 ---
 title: "Connect to Azure DevOps"
 id: "connect-azure-devops"
-pagination_next: "docs/cloud/git/setup-azure"
+pagination_next: "docs/cloud/git/setup-service-principal"
 ---
 
 # Connect to Azure DevOps <Lifecycle status="enterprise" />
@@ -20,12 +20,10 @@ Connect your Azure DevOps cloud account in dbt Cloud to unlock new product exper
 - Trigger Continuous integration (CI) builds when pull requests are opened in Azure DevOps.
 
 
-To connect Azure DevOps in dbt Cloud:
+Currently, there are multiple methods for integrating Azure DevOps with dbt Cloud: 
 
-1. An Entra ID admin role (or role with proper permissions) needs to [set up an Active Directory application](/docs/cloud/git/setup-azure#register-an-azure-ad-app).
-2. An Azure DevOps admin needs to [connect the accounts](/docs/cloud/git/setup-azure#connect-azure-devops-to-your-new-app). 
-3. A dbt Cloud account admin needs to [add the app to dbt Cloud](/docs/cloud/git/setup-azure#add-your-azure-ad-app-to-dbt-cloud).    
-4. dbt Cloud developers need to [personally authenticate with Azure DevOps](/docs/cloud/git/authenticate-azure) from dbt Cloud.
+- [**Service principal (recommended)**](/docs/cloud/git/setup-service-principal): Currently, this feature is in a phased rollout and not widely available to all accounts.
+- [**Service user (legacy)**](/docs/cloud/git/setup-service-user): Available to all accounts.
+- [**Service user to service principal migration**](/docs/cloud/git/setup-service-principal#migrate-to-service-principal): Once the **Service principal** option is available, you can migrate to the new service. 
 
-
-If you're a Business Critical customer using [IP restrictions](/docs/cloud/secure/ip-restrictions), ensure you've added the appropriate Azure DevOps CIDRs to your IP restriction rules, or else the Azure DevOps connection will fail.
+No matter which approach you take, you will need admins for dbt Cloud, Azure Entra ID, and Azure DevOps to complete the integration. For more information, follow the setup guide that's right for you.