Merge branch 'current' into b-per-patch-1

website/docs/docs/build/environment-variables.md

@@ -97,7 +97,7 @@ While all environment variables are encrypted at rest in dbt Cloud, dbt Cloud ha
 
 dbt Cloud has a number of pre-defined variables built in. Variables are set automatically and cannot be changed.
 
-**dbt Cloud IDE details**
+#### dbt Cloud IDE details
 
 The following environment variable is set automatically for the dbt Cloud IDE:
 
@@ -109,13 +109,16 @@ The following environment variable is set automatically for the dbt Cloud IDE:
 
 Use case — This is useful in cases where you want to dynamically use the Git branch name as a prefix for a [development schema](/docs/build/custom-schemas) ( `{{ env_var ('DBT_CLOUD_GIT_BRANCH') }}` ).
 
-**dbt Cloud context**
+#### dbt Cloud context
 
-The following environment variables are set automatically for deployment runs:
+The following environment variables are set automatically: 
 
-- `DBT_ENV`: This key is reserved for the dbt Cloud application and will always resolve to 'prod'
+- `DBT_ENV`: This key is reserved for the dbt Cloud application and will always resolve to 'prod'. For deployment runs only.
+- `DBT_CLOUD_ENVIRONMENT_NAME`: The name of the dbt Cloud environment in which `dbt` is running. 
+- `DBT_CLOUD_ENVIRONMENT_TYPE`: The type of dbt Cloud environment in which `dbt` is running. The valid values are `development` or `deployment`.
+
+#### Run details
 
-**Run details**
 - `DBT_CLOUD_PROJECT_ID`: The ID of the dbt Cloud Project for this run
 - `DBT_CLOUD_JOB_ID`: The ID of the dbt Cloud Job for this run
 - `DBT_CLOUD_RUN_ID`: The ID of this particular run
@@ -124,7 +127,7 @@ The following environment variables are set automatically for deployment runs:
 - `DBT_CLOUD_ENVIRONMENT_ID`: The ID of the environment for this run
 - `DBT_CLOUD_ACCOUNT_ID`: The ID of the dbt Cloud account for this run
 
-**Git details**
+#### Git details
 
 _The following variables are currently only available for GitHub, GitLab, and Azure DevOps PR builds triggered via a webhook_
 

website/docs/docs/build/saved-queries.md

@@ -102,24 +102,7 @@ saved_queries:
 ```
 </File>
 
-Note, you can set `export_as` to both the saved query and the exports [config](/reference/resource-properties/config), with the exports config value taking precedence. If a key isn't set in the exports config, it will inherit the saved query config value.
-
-#### Project-level saved queries
-
-To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
-
-<File name='dbt_project.yml'>
-
-```yaml
-saved-queries:
-  my_saved_query:
-    config:
-      +cache:
-        enabled: true
-```
-</File>
-
-For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
+Note, that you can set `export_as` to both the saved query and the exports [config](/reference/resource-properties/config), with the exports config value taking precedence. If a key isn't set in the exports config, it will inherit the saved query config value.
 
 #### Where clause
 
@@ -171,6 +154,26 @@ saved_queries:
 </File>
 </VersionBlock>
 
+<VersionBlock firstVersion="1.7">
+
+#### Project-level saved queries
+
+To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
+
+<File name='dbt_project.yml'>
+
+```yaml
+saved-queries:
+  my_saved_query:
+    config:
+      +cache:
+        enabled: true
+```
+</File>
+
+For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
+</VersionBlock>
+
 To build `saved_queries`, use the [`--resource-type` flag](/reference/global-configs/resource-type) and run the command `dbt build --resource-type saved_query`.
 
 ## Configure exports

website/docs/docs/dbt-versions/release-notes.md

@@ -20,9 +20,11 @@ Release notes are grouped by month for both multi-tenant and virtual private clo
 
 ## September 2024
 
+- **New:** There are two new [environment variable defaults](/docs/build/environment-variables#dbt-cloud-context) — `DBT_CLOUD_ENVIRONMENT_NAME` and `DBT_CLOUD_ENVIRONMENT_TYPE`.
 - **New:** The [Amazon Athena warehouse connection](/docs/cloud/connect-data-platform/connect-amazon-athena) is available as a public preview for dbt Cloud accounts that have upgraded to [`versionless`](/docs/dbt-versions/versionless-cloud).
 
 ## August 2024
+
 - **Fix:** Fixed an issue in [dbt Explorer](/docs/collaborate/explore-projects) where navigating to a consumer project from a public node resulted in displaying a random public model rather than the original selection. 
 - **New**: You can now configure metrics at granularities at finer time grains, such as hour, minute, or even by the second. This is particularly useful for more detailed analysis and for datasets where high-resolution time data is required, such as minute-by-minute event tracking. Refer to [dimensions](/docs/build/dimensions) for more information about time granularity.
 - **Enhancement**: Microsoft Excel now supports [saved selections](/docs/cloud-integrations/semantic-layer/excel#using-saved-selections) and [saved queries](/docs/cloud-integrations/semantic-layer/excel#using-saved-queries). Use Saved selections to save your query selections within the Excel application. The application also clears stale data in [trailing rows](/docs/cloud-integrations/semantic-layer/excel#other-settings) by default. To return your results and keep any previously selected data intact, un-select the **Clear trailing rows** option. 

website/plugins/buildRSSFeeds/index.js

@@ -8,13 +8,20 @@ module.exports = function buildRSSFeedsPlugin() {
   return {
     name: 'docusaurus-build-rss-feeds-plugin',
     async loadContent() {
+
+      // Skip generating RSS feeds in non-production environments
+      if (process.env.VERCEL_ENV !== "production") {
+        console.log('RSS Feeds are only generated in production. Skipping creation of RSS Feed.')
+        return null
+      }
+
       // Release Notes directory
       const releaseNotesDirectory = 'docs/docs/dbt-versions/release-notes'
 
       // Get all files and file data within all release notes directories
       const releaseNotesFiles = getDirectoryFiles(releaseNotesDirectory, [], true)
 
-      if(!releaseNotesFiles || !releaseNotesFiles.length) 
+      if (!releaseNotesFiles || !releaseNotesFiles.length)
         return null
 
       // Generate RSS feeds