Merge pull request #539 from hashicorp/repo-sync

Repo sync

Author: LeahMarieBush

.github/actions/reload-dev-portal/action.yml

@@ -20,6 +20,10 @@ inputs:
     description: 'Revalidate token'
     required: true
     type: string
+  bot-bypass-token:
+    description: 'Bot bypass token'
+    required: true
+    type: string
 
 runs:
   using: "composite"
@@ -73,8 +77,10 @@ runs:
       env:
         url: 'https://developer.hashicorp.com/api/revalidate/paths'
         auth: 'Authorization: Bearer ${{ inputs.revalidate-token }}'
+        bot-bypass: '${{ inputs.bot-bypass-token }}'
       run: |
         curl -X POST "${{ env.url }}" \
           -H "${{ env.auth }}" \
           -H "Content-Type: application/json" \
+          -H "X-BOT-BYPASS: ${{ env.bot-bypass }}" \
           -d '{"paths": ${{ steps.map-files.outputs.FILES_URLS }} }'

.github/labeler.yml

@@ -1,6 +1,77 @@
 # Copyright (c) HashiCorp, Inc.
 # SPDX-License-Identifier: BUSL-1.1
 
+# Add 'Boundary' label to changes under 'content/boundary'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# Boundary        | Default; applies to all doc updates
+# Boundary        | Updates on HCP Boundary in hcp-docs directory
+
+Boundary:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/boundary/**',
+        'content/hcp-docs/content/docs/boundary/**'
+      ]
+
+# Add 'Consul' label to changes under 'content/consul'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# Consul          | Default; applies to all doc updates
+# Consul          | Updates on HCP Consul in hcp-docs directory
+
+Consul:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/consul/**',
+        'content/hcp-docs/content/docs/consul/**'
+      ]
+
+# Add 'HCP' label to changes under 'content/hcp-docs'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# HCP             | Default; applies to all doc updates
+
+HCP:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/hcp-docs/**'
+      ]
+
+# Add 'Packer' label to changes under 'content/packer'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# Packer          | Default; applies to all doc updates
+# Packer          | Updates on HCP Packer in hcp-docs directory
+
+Packer:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/packer/**',
+        'content/hcp-docs/content/docs/packer/**'
+      ]
+
+# Add 'Sentinel' label to changes under 'content/sentinel'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# Sentinel        | Default; applies to all doc updates
+
+Sentinel:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/sentinel/**'
+      ]
+
 # Add a Terraform label to changes under the related folders:
 #
 # Folder                      | Labels
@@ -66,19 +137,35 @@ TF Plugin Framework:
         'content/terraform-plugin-framework/**'
       ]
 
+# Add 'Vagrant' label to changes under 'content/vagrant'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# Vagrant         | Default; applies to all doc updates
+# Vagrant         | Updates on HCP Vagrant in hcp-docs directory
 
-# Add 'Vault' label to changes under 'content/vault'
+Vagrant:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/vagrant/**',
+        'content/hcp-docs/content/docs/vagrant/**'
+      ]
+
+# Add 'Vault' label to changes under 'content/vault', and 'content/hcp-docs/content/docs/vault'
 #
 # Label           | Rule
 # --------------- | ------------------------------------------------------------
 # Vault           | Default; applies to all doc updates
+# Vault           | Updates on HCP Vault Dedicated in hcp-docs directory
 # Vault IC update | Updates on "Important changes" related docs
 
 Vault:
 - any:
   - changed-files:
     - any-glob-to-any-file: [
-        'content/vault/**'
+        'content/vault/**',
+        'content/hcp-docs/content/docs/vault/**'
       ]
 
 Vault IC:
@@ -91,6 +178,19 @@ Vault IC:
         'content/vault/*/content/docs/updates/lts-tracker.mdx'
       ]
 
+# Add 'Vault Radar' label to changes under 'content/hcp-docs/content/docs/vault-radar'
+#
+# Label           | Rule
+# --------------- | ------------------------------------------------------------
+# Vault Radar     | Default; applies to all doc updates
+
+Vault Radar:
+- any:
+  - changed-files:
+    - any-glob-to-any-file: [
+        'content/hcp-docs/content/docs/vault-radar/**'
+      ]
+
 # Add 'WAF' label to changes under 'content/well-architected-framework'
 #
 # Label           | Rule
@@ -104,15 +204,15 @@ WAF:
         'content/well-architected-framework/**'
       ]
 
-# Add 'Sentinel' label to changes under 'content/sentinel'
+# Add 'Waypoint' label to changes under 'content/hcp-docs/content/docs/waypoint'
 #
 # Label           | Rule
 # --------------- | ------------------------------------------------------------
-# Sentinel        | Default; applies to all doc updates
+# Waypoint        | Default; applies to all doc updates
 
-Sentinel:
+Waypoint:
 - any:
   - changed-files:
     - any-glob-to-any-file: [
-        'content/sentinel/**'
-      ]
+        'content/hcp-docs/content/docs/waypoint/**'
+      ]

.github/workflows/deploy-udr.yml

@@ -58,3 +58,4 @@ jobs:
           head_sha: ${{ github.event.after }}
           dev-portal-deploy-hook-prod: ${{ secrets.DEV_PORTAL_DEPLOY_HOOK_PROD }}
           revalidate-token: ${{ secrets.REVALIDATE_TOKEN }}
+          bot-bypass-token: ${{ secrets.DEVELOPER_BOT_BYPASS_TOKEN }}  

.github/workflows/force-reload-dev-portal.yml

@@ -31,3 +31,4 @@ jobs:
           head_sha: ${{ inputs.head_sha }}
           dev-portal-deploy-hook-prod: ${{ secrets.DEV_PORTAL_DEPLOY_HOOK_PROD }}
           revalidate-token: ${{ secrets.REVALIDATE_TOKEN }}
+          bot-bypass-token: ${{ secrets.DEVELOPER_BOT_BYPASS_TOKEN }}

content/terraform-docs-agents/v1.25.x/docs/cloud-docs/agents/changelog.mdx

@@ -18,6 +18,12 @@ within each release are categorized into one or more of the following labels:
 Each version below corresponds to a release artifact available for download on
 the official [releases website](https://releases.hashicorp.com/tfc-agent/).
 
+## 1.25.1 (10/14/2025)
+
+SECURITY:
+
+* Updated Docker image to address various OpenSSL CVEs (#1213)
+
 ## 1.25.0 (09/30/2025)
 
 FEATURES:

content/terraform-docs-common/data/cloud-docs-nav-data.json

@@ -298,11 +298,11 @@
       {
         "title": "Import existing resources",
         "path": "workspaces/import",
+        "alias": "search, terraform search, resource discoverability",
         "badge": {
           "text": "BETA",
           "type": "outlined",
           "color": "neutral"
-
         }
       },
       {

content/terraform-docs-common/docs/cloud-docs/api-docs/change-requests.mdx

@@ -250,12 +250,12 @@ You must specify the following fields in your payload when creating a new change
 
 | Key path   | Type | Required | Description |
 |------------|------|---------|-------------|
-| `data.action_type`          | string |   Required   | The action to take. To create a change request, specify `"change_request"`. |
-| `data.action_inputs`        | object |   Required   | Arguments for the bulk action. |
-| `data.action_inputs.subject` | string |  Required   | The change request's subject line.
-| `data.action_inputs.message` | string |   Required   | The change request's message, which HCP Terraform treats as markdown. |
-| `data.target_ids`           | array  |   Optional   | The IDs of the workspace you want to associate with this change request. You do not need to specify this field if you provide `data.query`. |
-| `data.query`                | object |    Optional  | An [explorer query](/terraform/cloud-docs/api-docs/explorer#execute-a-query) with workspace data. You do not need to specify this field if you provide `data.target_ids`. |
+| `data.attributes.action_type`          | string |   Required   | The action to take. To create a change request, specify `"change_request"`. |
+| `data.attributes.action_inputs`        | object |   Required   | Arguments for the bulk action. |
+| `data.attributes.action_inputs.subject` | string |  Required   | The change request's subject line.
+| `data.attributes.action_inputs.message` | string |   Required   | The change request's message, which HCP Terraform treats as markdown. |
+| `data.attributes.target_ids`           | array  |   Optional   | The IDs of the workspace you want to associate with this change request. You do not need to specify this field if you provide `data.attribute.query`. |
+| `data.attributes.query`                | object |    Optional  | An [explorer query](/terraform/cloud-docs/api-docs/explorer#execute-a-query) with workspace data. You do not need to specify this field if you provide `data.attribute.target_ids`. |
 
 ### Sample Payload
 
@@ -269,15 +269,20 @@ You must specify the following fields in your payload when creating a new change
         "subject": "[Action Required] Github Actions Pinning (SEC-090)",
         "message": "Some long description here",
       },
-    "query": {
-      "type": "workspaces",
-      "filter": [
-        "field": "workspace_name",
-        "operator": "contains",
-        "value": ["dev"]
-      ]
+      "query": {
+        "type": "workspaces",
+        "filter": [
+          {
+            "workspace_name": {
+              "contains": [
+                "dev"
+              ]
+            }
+          }
+        ]
+      }
     }
-  },
+  }
 }
 ```
 

content/terraform-docs-common/docs/cloud-docs/api-docs/projects.mdx

@@ -115,7 +115,7 @@ Properties without a default value are required.
               "key": "environment",
               "value": "development"
             }
-          },
+          }
         ]
       }
     }

content/terraform-docs-common/docs/cloud-docs/workspaces/import.mdx

@@ -1,18 +1,18 @@
 ---
-page_title: Import existing resources to state
-description: Learn how to use queries to find unmanaged infrastructure and import it into Terraform
+page_title: Use search to find and import existing resources to state
+description: Learn how to use Terraform search to find unmanaged infrastructure and import it into your workspace in bulk.
 tfc_only: true
 ---
 
 # Import existing resources to state
 
-You can define queries in your Terraform configuration to search for resources that are not yet managed by Terraform. HCP Terraform presents query results so that you can use the UI to import the resources and begin managing them as code. This topic describes the workflow for importing resources in bulk. For instructions on importing single resources or small batches of resources in your configuration, refer to [Import a single resource](/terraform/language/v1.14.x/import/single-resource). 
+Terraform can search your existing infrastructure for resources to let you import any unmanaged resources to an HCP Terraform workspace in bulk. For instructions on importing single resources or small batches of resources in your configuration, refer to [Import a single resource](/terraform/language/v1.14.x/import/single-resource). 
 
 @include 'beta.mdx'
 
 ## Overview
 
-You can use search functionality in [UI and VCS-driven](/terraform/cloud-docs/run/ui) and [CLI-driven](/terraform/cloud-docs/run/cli) workspaces. Complete the following steps to search for resources and import them into your Terraform state:
+You can search for unmanaged resources in [UI and VCS-driven](/terraform/cloud-docs/run/ui) and [CLI-driven](/terraform/cloud-docs/run/cli) workspaces. HCP Terraform presents results so that you can use the UI to import the resources and begin managing them as code. Complete the following steps to search for resources and import them into your Terraform state:
 
 1. **Define queries**: Add `list` blocks to your Terraform configuration. If you are using the VCS-driven workflow, commit this change and push it to the repository associated with your workspace in HCP Terraform. Refer to [Import resources in bulk](/terraform/language/v1.14.x/import/bulk) for more information.
 1. **Run the queries**: You can run queries in the HCP Terraform UI or run the Terraform CLI on your local workstation.

content/terraform/v1.13.x/docs/language/modules/configuration.mdx

@@ -66,7 +66,7 @@ Add the `depth` query parameter to the `source` URL and specify how many commits
 
 The following module sources support shallow clones:
 
-- [GitHub repositoris](/terraform/language/block/module#github-repository)
+- [GitHub repositories](/terraform/language/block/module#github-repository)
 - [Git repositories](/terraform/language/block/module#git-repository)
 - [BitBucket repositories](/terraform/language/block/module#bitbucket-repository)
 
@@ -179,4 +179,4 @@ removed {
 }
 ```
 
-Refer to [`moved` block reference](/terraform/language/block/removed) for more information.
+Refer to [`moved` block reference](/terraform/language/block/removed) for more information.