Merge branch 'current' into amychen1776-patch-8

dbt-labs · Dec 11, 2023 · b5070a8 · b5070a8
2 parents 5825cd0 + 444ec87
commit b5070a8
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 7 deletions.
diff --git a/website/docs/best-practices/dbt-unity-catalog-best-practices.md b/website/docs/best-practices/dbt-unity-catalog-best-practices.md
@@ -49,9 +49,9 @@ The **prod** service principal should have “read” access to raw source data,
 
 |  | Source Data | Development catalog | Production catalog | Test catalog |
 | --- | --- | --- | --- | --- |
-| developers | use | use, create table & create view | use or none | none |
-| production service principal | use | none | use, create table & create view | none |
-| Test service principal | use | none | none | use, create table & create view |
+| developers | use | use, create schema, table, & view | use or none | none |
+| production service principal | use | none | use, create schema, table & view | none |
+| Test service principal | use | none | none | use, create schema, table & view |
 
 
 ## Next steps

diff --git a/website/docs/docs/cloud/about-cloud/regions-ip-addresses.md b/website/docs/docs/cloud/about-cloud/regions-ip-addresses.md
@@ -12,7 +12,7 @@ dbt Cloud is [hosted](/docs/cloud/about-cloud/architecture) in multiple regions
 | Region | Location | Access URL | IP addresses | Developer plan | Team plan | Enterprise plan |
 |--------|----------|------------|--------------|----------------|-----------|-----------------|
 | North America multi-tenant [^1] | AWS us-east-1 (N. Virginia) | cloud.getdbt.com | 52.45.144.63 <br /> 54.81.134.249 <br />52.22.161.231 <br />52.3.77.232 <br />3.214.191.130 <br />34.233.79.135 | ✅ | ✅ | ✅ |
-| North America Cell 1 [^1]       | AWS us-east-1 (N. Virginia) | {account prefix}.us1.dbt.com | 52.45.144.63 <br /> 54.81.134.249 <br />52.22.161.231 <br />52.3.77.232 <br />3.214.191.130 <br />34.233.79.135 | ❌ | ❌ | ✅ |
+| North America Cell 1 [^1]       | AWS us-east-1 (N. Virginia) | {account prefix}.us1.dbt.com | 52.45.144.63 <br /> 54.81.134.249 <br />52.22.161.231 <br />52.3.77.232 <br />3.214.191.130 <br />34.233.79.135 | ✅  | ❌ | ✅ |
 | EMEA [^1] | AWS eu-central-1	(Frankfurt) | emea.dbt.com | 3.123.45.39 <br /> 3.126.140.248 <br /> 3.72.153.148 | ❌ | ❌ | ✅ |
 | APAC  [^1] | 	AWS ap-southeast-2  (Sydney)| au.dbt.com | 52.65.89.235 <br /> 3.106.40.33 <br /> 13.239.155.206 <br />| ❌ | ❌ | ✅ |
 | Virtual Private dbt or Single tenant | Customized |  Customized | Ask [Support](/community/resources/getting-help#dbt-cloud-support) for your IPs | ❌ | ❌ | ✅ |

diff --git a/website/docs/docs/dbt-cloud-apis/schema-discovery-job.mdx b/website/docs/docs/dbt-cloud-apis/schema-discovery-job.mdx
@@ -61,4 +61,4 @@ query JobQueryExample {
 ### Fields
 When querying an `job`, you can use the following fields.
 
-<SchemaTable nodeName="JobNode" />
+<SchemaTable nodeName="JobNode" exclude={['metric', 'metrics']} />
diff --git a/website/docs/docs/dbt-cloud-apis/schema.jsx b/website/docs/docs/dbt-cloud-apis/schema.jsx
@@ -173,7 +173,7 @@ export const NodeArgsTable = ({ parent, name, useBetaAPI }) => {
   )
 }
 
-export const SchemaTable = ({ nodeName, useBetaAPI }) => {
+export const SchemaTable = ({ nodeName, useBetaAPI, exclude = [] }) => {
   const [data, setData] = useState(null)
   useEffect(() => {
     const fetchData = () => {
@@ -255,6 +255,7 @@ export const SchemaTable = ({ nodeName, useBetaAPI }) => {
       </thead>
       <tbody>
         {data.data.__type.fields.map(function ({ name, description, type }) {
+          if (exclude.includes(name)) return;
           return (
             <tr key={name}>
               <td><code>{name}</code></td>

diff --git a/website/docs/guides/set-up-your-databricks-dbt-project.md b/website/docs/guides/set-up-your-databricks-dbt-project.md
@@ -62,7 +62,7 @@ Let’s [create a Databricks SQL warehouse](https://docs.databricks.com/sql/admi
 5. Click *Create*
 6. Configure warehouse permissions to ensure our service principal and developer have the right access.
 
-We are not covering python in this post but if you want to learn more, check out these [docs](https://docs.getdbt.com/docs/build/python-models#specific-data-platforms). Depending on your workload, you may wish to create a larger SQL Warehouse for production workflows while having a smaller development SQL Warehouse (if you’re not using Serverless SQL Warehouses).
+We are not covering python in this post but if you want to learn more, check out these [docs](https://docs.getdbt.com/docs/build/python-models#specific-data-platforms). Depending on your workload, you may wish to create a larger SQL Warehouse for production workflows while having a smaller development SQL Warehouse (if you’re not using Serverless SQL Warehouses). As your project grows, you might want to apply [compute per model configurations](/reference/resource-configs/databricks-configs#specifying-the-compute-for-models). 
 
 ## Configure your dbt project