From 7389ad9fd15212192a79c6a92cc9e7c325fb6825 Mon Sep 17 00:00:00 2001
From: Ben Cassell <98852248+benc-db@users.noreply.github.com>
Date: Thu, 30 Nov 2023 13:31:49 -0800
Subject: [PATCH] Update
 website/docs/reference/resource-configs/databricks-configs.md

Co-authored-by: Amy Chen <46451573+amychen1776@users.noreply.github.com>
---
 .../docs/reference/resource-configs/databricks-configs.md  | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/website/docs/reference/resource-configs/databricks-configs.md b/website/docs/reference/resource-configs/databricks-configs.md
index e4027edaf2e..bb226045788 100644
--- a/website/docs/reference/resource-configs/databricks-configs.md
+++ b/website/docs/reference/resource-configs/databricks-configs.md
@@ -423,7 +423,14 @@ Each compute is keyed by a name which is used in the model definition/configurat
 You need to use the same set of names for compute across your outputs, though you may supply different http_paths, allowing you to use different computes in different deployment scenarios.
 
 :::
+To configure this inside of dbt Cloud, use the [extended attributes feature](/docs/dbt-cloud-environments#extended-attributes-) on the desired environments. You can input them as such.
 
+```yaml
+compute:
+  Compute1:
+    http_path:[`/some/other/path']
+  Compute2:
+    http_path:[`/some/other/path']
 ### Specifying the compute for models
 
 As with many other configuaration options, you can specify the compute for a model in multiple ways, using `databricks_compute`.