Merge branch 'main' into TFDN-1107-add-agent-sort-docs

Author: twitnithegirl

content/terraform-docs-common/docs/cloud-docs/workspaces/dynamic-provider-credentials/vault-configuration.mdx

@@ -111,8 +111,9 @@ To understand all the available options for matching bound claims, refer to the
 !> **Warning:** you should always check, at minimum, the audience and the name of the organization in order to prevent unauthorized access from other HCP Terraform organizations!
 
 #### Token TTLs
-We recommend setting token_ttl to a relatively short value. HCP Terraform can renew the token periodically until the plan or apply is complete, then revoke it to prevent it from being used further.
+We recommend creating a role which issues a renewable token, and setting `token_ttl` to a relatively short value, such as 20 minutes. HCP Terraform can renew the token periodically until the plan or apply is complete, then revoke it to prevent it from being used further.
 
+If you use a non-renewable token with HCP Terraform, the `token_ttl` has a maximum limit of 2 hours. If you use a non-renewable token with Terraform Enterprise, then the `token_ttl` of that token must match or exceed the [run phase timeout](/terraform/enterprise/application-administration/general#terraform-run-timeout-settings).
 ## Configure HCP Terraform
 You’ll need to set some environment variables in your HCP Terraform workspace in order to configure HCP Terraform to authenticate with Vault using dynamic credentials. You can set these as workspace variables, or if you’d like to share one Vault role across multiple workspaces, you can use a variable set. When you configure dynamic provider credentials with multiple provider configurations of the same type, use either a default variable or a tagged alias variable name for each provider configuration. Refer to [Specifying Multiple Configurations](#specifying-multiple-configurations) for more details.
 

content/terraform-enterprise/1.0.x/docs/enterprise/deploy/kubernetes/index.mdx

@@ -213,17 +213,6 @@ env:
     TFE_REDIS_PASSWORD: '<Redis password>'
     TFE_LICENSE: <Hashicorp license>
     TFE_ENCRYPTION_PASSWORD: '<Encryption password>'
-    TFE_REDIS_USE_MTLS: <To use mtls with Redis standalone or Sentinel? eg. "false">
-    TFE_REDIS_CLIENT_CERT_PATH: <Path to the client certificate file to be used for mTLS authentication with Redis server>
-    TFE_REDIS_CA_CERT_PATH: <Path to the Certificate Authority file user to validate the certificate>
-    TFE_REDIS_CLIENT_KEY_PATH: <Path to the private key file corresponding to the client certificate>
-    TFE_REDIS_SIDEKIQ_USE_MTLS: <To use mtls with Redis Enterprise? eg. "false">
-    TFE_REDIS_SIDEKIQ_CLIENT_CERT_PATH: <Path to the client certificate file to be used for mTLS authentication with Redis server>
-    TFE_REDIS_SIDEKIQ_CA_CERT_PATH: <Path to the Certificate Authority file user to validate the certificate>
-    TFE_REDIS_SIDEKIQ_CLIENT_KEY_PATH: <Path to the private key file corresponding to the client certificate>
-    TFE_REDIS_SENTINEL_ENABLED: <To use sentinel? e.g. "false">
-    TFE_REDIS_SENTINEL_HOSTS: <Hostname and port of Sentinel hosts, e.g. sentinel.example.com:26379>
-    TFE_REDIS_SENTINEL_LEADER_NAME: <Name of the Sentinel leader>
 ```
 
 ### Google Kubernetes Engine (GKE)
@@ -254,17 +243,6 @@ env:
     TFE_REDIS_USE_TLS: <To use tls? eg. "false">
     TFE_REDIS_USE_AUTH: <To use customized credential to authenticate? eg. "true">
     TFE_REDIS_USER: <Redis username>
-    TFE_REDIS_USE_MTLS: <To use mtls with Redis standalone or Sentinel? eg. "false">
-    TFE_REDIS_CLIENT_CERT_PATH: <Path to the client certificate file to be used for mTLS authentication with Redis server>
-    TFE_REDIS_CA_CERT_PATH: <Path to the Certificate Authority file user to validate the certificate>
-    TFE_REDIS_CLIENT_KEY_PATH: <Path to the private key file corresponding to the client certificate>
-    TFE_REDIS_SIDEKIQ_USE_MTLS: <To use mtls with Redis Enterprise? eg. "false">
-    TFE_REDIS_SIDEKIQ_CLIENT_CERT_PATH: <Path to the client certificate file to be used for mTLS authentication with Redis server>
-    TFE_REDIS_SIDEKIQ_CA_CERT_PATH: <Path to the Certificate Authority file user to validate the certificate>
-    TFE_REDIS_SIDEKIQ_CLIENT_KEY_PATH: <Path to the private key file corresponding to the client certificate>
-    TFE_REDIS_SENTINEL_ENABLED: <To use sentinel? e.g. "false">
-    TFE_REDIS_SENTINEL_HOSTS: <Hostname and port of Sentinel hosts, e.g. sentinel.example.com:26379>
-    TFE_REDIS_SENTINEL_LEADER_NAME: <Name of the Sentinel leader>
 
     # Google Cloud Storage settings.
     TFE_OBJECT_STORAGE_TYPE: google
@@ -307,17 +285,6 @@ env:
     TFE_REDIS_USE_TLS: <To use tls? eg. "false">
     TFE_REDIS_USE_AUTH: <To use customized credential to authenticate? eg. "true">
     TFE_REDIS_USER: <Redis username>
-    TFE_REDIS_USE_MTLS: <To use mtls with Redis standalone or Sentinel? eg. "false">
-    TFE_REDIS_CLIENT_CERT_PATH: <Path to the client certificate file to be used for mTLS authentication with Redis server>
-    TFE_REDIS_CA_CERT_PATH: <Path to the Certificate Authority file user to validate the certificate>
-    TFE_REDIS_CLIENT_KEY_PATH: <Path to the private key file corresponding to the client certificate>
-    TFE_REDIS_SIDEKIQ_USE_MTLS: <To use mtls with Redis Enterprise? eg. "false">
-    TFE_REDIS_SIDEKIQ_CLIENT_CERT_PATH: <Path to the client certificate file to be used for mTLS authentication with Redis server>
-    TFE_REDIS_SIDEKIQ_CA_CERT_PATH: <Path to the Certificate Authority file user to validate the certificate>
-    TFE_REDIS_SIDEKIQ_CLIENT_KEY_PATH: <Path to the private key file corresponding to the client certificate>
-    TFE_REDIS_SENTINEL_ENABLED: <To use sentinel? e.g. "false">
-    TFE_REDIS_SENTINEL_HOSTS: <Hostname and port of Sentinel hosts, e.g. sentinel.example.com:26379>
-    TFE_REDIS_SENTINEL_LEADER_NAME: <Name of the Sentinel leader>
 
     # Azure container storage settings.
     TFE_OBJECT_STORAGE_TYPE: azure

content/terraform-enterprise/1.0.x/docs/enterprise/deploy/manage/upgrade.mdx

@@ -21,6 +21,8 @@ Complete the following steps to upgrade Terraform Enterprise:
 
 1. If your deployment is configured to run multiple `terraform-enterprise` nodes, scale down to a single node. You can run multiple nodes when Terraform Enterprise is in `active-active` mode. Refer to  [Configure the operational mode](/terraform/enterprise/deploy/configuration/storage/configure-mode) for additional information.
 
+1. If your deployment makes use of an autoscaling group to manage instances of Terraform Enterprise, disable any configured health checks that would trigger the autoscaling group to rotate Terraform Enterprise instances during an upgrade.
+
 1. Stop the Terraform Enterprise application.
 
   <Tabs>

content/terraform-enterprise/1.0.x/docs/enterprise/releases/1.0.x/index.mdx

@@ -14,6 +14,7 @@ Below is a list of the most recent Terraform Enterprise Releases that can deploy
 
 | Version           | Linked <br />Terraform CLI\**                                     | Sentinel                                                                    | Tested Kubernetes Versions (EKS, AKS, GKE) | Helm Chart Version |
 | ----------------- | ------------------------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------------ | ------------------ |
+| [1.0.1](#1-0-1)   | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  |  [1.33](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html), [1.33](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions?tabs=azure-cli#aks-kubernetes-release-calendar), [1.32](https://cloud.google.com/kubernetes-engine/docs/release-notes)                  | [1.6.5](https://github.com/hashicorp/terraform-enterprise-helm/releases/tag/v1.6.5)       |
 | [1.0.0](#1-0-0)   | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  |  [1.33](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html), [1.33](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions?tabs=azure-cli#aks-kubernetes-release-calendar), [1.32](https://cloud.google.com/kubernetes-engine/docs/release-notes)                  | [1.6.5](https://github.com/hashicorp/terraform-enterprise-helm/releases/tag/v1.6.5)       |
 
 
@@ -24,6 +25,7 @@ Below is a list of the most recent Terraform Enterprise Releases that can deploy
 
 | Version           | Linked <br />Terraform CLI\**                                     | Sentinel                                                                    | Recommended Docker Compose version |
 | ----------------- | ------------------------------------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------- |
+| [1.0.1](#1-0-1)   | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  | [V2](https://docs.docker.com/compose/migrate/)                       |
 | [1.0.0](#1-0-0)   | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  | [V2](https://docs.docker.com/compose/migrate/)                       |
 
 
@@ -34,6 +36,7 @@ Below is a list of the most recent Terraform Enterprise Releases that can deploy
 
 | Version           | Linked <br />Terraform CLI\**                                     | Sentinel                                                                    | Tested Podman version |
 | ----------------- | ------------------------------------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------- |
+| [1.0.1](#1-0-1)   | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  | [v5](https://github.com/containers/podman/releases/tag/v5.0.0)                       |
 | [1.0.0](#1-0-0)   | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  | [v5](https://github.com/containers/podman/releases/tag/v5.0.0)                       |
 
 
@@ -44,6 +47,7 @@ Below is a list of the most recent Terraform Enterprise Releases that can deploy
 
 | Version           | Linked <br />Terraform CLI\**                                       | Sentinel                                                                    | Tested Nomad versions       | Min supported version |
 | ----------------- | ------------------------------------------------------------------- | --------------------------------------------------------------------------- | --------------------------- | --------------------- |
+| [1.0.1](#1-0-1)  | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  | 1.7 | 1.5 |
 | [1.0.0](#1-0-0)  | [1.12.1](https://github.com/hashicorp/terraform/releases/tag/v1.12.1) | [0.40.0](https://developer.hashicorp.com/sentinel/docs/changelog#0-40-0-may-12-2025)  | 1.7 | 1.5 |
 
   </Tab>
@@ -53,7 +57,22 @@ Below is a list of the most recent Terraform Enterprise Releases that can deploy
 
 \** The release package contains this version of the Terraform CLI, but you can install older and newer versions of the Terraform CLI as needed via the Admin [UI](/terraform/enterprise/application-administration/resources#managing-terraform-versions) or [API](/terraform/enterprise/api-docs/admin/terraform-versions).
 
-\+ This release is unavailable.
+## 1.0.1
+<span class="h4-size">2025-09-15</span>
+
+Last required release: [v202406-1 (776)](/terraform/enterprise/releases/2024/v202406-1)
+
+Flexible Deployment Options `terraform-enterprise` container digest: amd64/linux `sha256:edc06293b395e5beb3dfbbda4e89341334ab184c5895b81cf31c074dadc43ff7`, arm64/linux `sha256:7d7dfa2b283f252b8a65b1689a49db2b3a0b81fcaefd11a560a93baf8ad6041f`
+
+## Deprecations
+1. Redis 6.0 will be officially deprecated as of the November release.
+2. As part of the upcoming release, the `tfectl db *` commands will be marked for deprecation.
+
+## Bug Fixes
+1. This release fixes a bug for Terraform Enterprise installs that make use of Redis with mTLS where the archivist service exited early.
+
+## Security
+1. Security vulnerabilities have been addressed and resolved in this update to enhance overall system protection.
 
 ## 1.0.0
 <span class="h4-size">2025-08-11</span>

content/terraform-enterprise/1.0.x/docs/enterprise/releases/index.mdx

@@ -10,7 +10,9 @@ description: >-
 
 <Tip title="Next Release">
 
-The next release 1.0.1 is scheduled for the week of September 15, 2025
+The next patch release for 1.0.x is scheduled for the week of October 11, 2025 
+
+The next minor release for 1.1.x is scheduled for the week of November 11, 2025
 
 </Tip>
 

content/terraform-enterprise/v202501-1/docs/enterprise/deploy/manage/upgrade.mdx

@@ -21,6 +21,8 @@ Complete the following steps to upgrade Terraform Enterprise:
 
 1. If your deployment is configured to run multiple `terraform-enterprise` nodes, scale down to a single node. You can run multiple nodes when Terraform Enterprise is in `active-active` mode. Refer to  [Configure the operational mode](/terraform/enterprise/deploy/configuration/storage/configure-mode) for additional information.
 
+1. If your deployment makes use of an autoscaling group to manage instances of Terraform Enterprise, disable any configured health checks that would trigger the autoscaling group to rotate Terraform Enterprise instances during an upgrade.
+
 1. Stop the Terraform Enterprise application.
 
   <Tabs>

content/terraform-enterprise/v202502-1/docs/enterprise/deploy/manage/upgrade.mdx

@@ -21,6 +21,8 @@ Complete the following steps to upgrade Terraform Enterprise:
 
 1. If your deployment is configured to run multiple `terraform-enterprise` nodes, scale down to a single node. You can run multiple nodes when Terraform Enterprise is in `active-active` mode. Refer to  [Configure the operational mode](/terraform/enterprise/deploy/configuration/storage/configure-mode) for additional information.
 
+1. If your deployment makes use of an autoscaling group to manage instances of Terraform Enterprise, disable any configured health checks that would trigger the autoscaling group to rotate Terraform Enterprise instances during an upgrade.
+
 1. Stop the Terraform Enterprise application.
 
   <Tabs>

content/terraform-enterprise/v202502-2/docs/enterprise/deploy/manage/upgrade.mdx

@@ -21,6 +21,8 @@ Complete the following steps to upgrade Terraform Enterprise:
 
 1. If your deployment is configured to run multiple `terraform-enterprise` nodes, scale down to a single node. You can run multiple nodes when Terraform Enterprise is in `active-active` mode. Refer to  [Configure the operational mode](/terraform/enterprise/deploy/configuration/storage/configure-mode) for additional information.
 
+1. If your deployment makes use of an autoscaling group to manage instances of Terraform Enterprise, disable any configured health checks that would trigger the autoscaling group to rotate Terraform Enterprise instances during an upgrade.
+
 1. Stop the Terraform Enterprise application.
 
   <Tabs>

content/terraform-enterprise/v202503-1/docs/enterprise/deploy/manage/upgrade.mdx

@@ -21,6 +21,8 @@ Complete the following steps to upgrade Terraform Enterprise:
 
 1. If your deployment is configured to run multiple `terraform-enterprise` nodes, scale down to a single node. You can run multiple nodes when Terraform Enterprise is in `active-active` mode. Refer to  [Configure the operational mode](/terraform/enterprise/deploy/configuration/storage/configure-mode) for additional information.
 
+1. If your deployment makes use of an autoscaling group to manage instances of Terraform Enterprise, disable any configured health checks that would trigger the autoscaling group to rotate Terraform Enterprise instances during an upgrade.
+
 1. Stop the Terraform Enterprise application.
 
   <Tabs>

content/terraform-enterprise/v202504-1/docs/enterprise/deploy/manage/upgrade.mdx

@@ -21,6 +21,8 @@ Complete the following steps to upgrade Terraform Enterprise:
 
 1. If your deployment is configured to run multiple `terraform-enterprise` nodes, scale down to a single node. You can run multiple nodes when Terraform Enterprise is in `active-active` mode. Refer to  [Configure the operational mode](/terraform/enterprise/deploy/configuration/storage/configure-mode) for additional information.
 
+1. If your deployment makes use of an autoscaling group to manage instances of Terraform Enterprise, disable any configured health checks that would trigger the autoscaling group to rotate Terraform Enterprise instances during an upgrade.
+
 1. Stop the Terraform Enterprise application.
 
   <Tabs>