HashiCorp Developer AI Private beta now available Sign up today
Terraform
Terraform Home

You are viewing documentation for version v202407-1. View latest version.

Terraform Enterprise v202406-1 (776)

This is a required release!

Flexible Deployment Options terraform-enterprise container digest: amd64/linux sha256:2d6cadbc5b4956fbebe899a0ca3735108aa3fa086d380215c45298dcfc4b9c31

Known Issues

  1. [Updated September 6, 2024] This release contains a possible migration error due to orphaned team membership records referring to teams that have been deleted. If this issue affects you, the upgrade will fail. To avoid this, please refer to our support article for steps to check if you have orphaned records and how to remove them before proceeding with the migration.
  2. [Updated June 26, 2024] After successfully running a database restore in mounted disk mode, the Terraform Enterprise container, or Replicated application, must be fully stopped and restarted in order for the application to run properly.
  3. [Updated August 14, 2024] Runs that rely on dynamic provider credentials and workload identity will fail after a certain number of signing key rotations. This problem is fixed in v202407-1, and you can avoid it by upgrading v202407-1 or above. For details on additional workarounds, including manually trimming keys, refer to our support article.

Deprecations

  1. Terraform Enterprise now supports new deployment options and will end support for the Replicated Native Scheduler option. The final Replicated release of Terraform Enterprise will be in November 2024. HashiCorp will support this release until April 1, 2026.

    To ensure you continue to receive the latest features and fixes, including security updates, please plan to migrate to a new deployment option by November 2024. For more information, check out Flexible Deployment Options or contact your HashiCorp account representative.

  2. RedHat Enterprise is ending support for RHEL v7 on June 30th, 2024. Following suit, Terraform Enterprise will no longer support RHEL v7 after June 30th, 2024. Replicated installations of Terraform Enterprise support RHEL 8. The Podman deployment option supports using RHEL 8 or higher.

  3. We've removed the organizations list and navigation items from the account settings page, and instead recommend referencing your main organization page for a list of your organizations.

Highlights

  1. This Terraform Enterprise release (v202406-1) is required, because of an upgrade of the internal PostgreSQL service from v14 to v16. This database upgrade also enables using the backup and restore API endpoints against external PostgreSQL servers running versions 15 or 16. If your upgrade fails, restore your PostgresQL v14 database.
  2. Terraform Enterprise now supports a new Flexible deployment option. Terraform Enterprise can now be deployed to HashiCorp Nomad. The feature is still in Beta stage. To get started, check out the Nomad Beta requirements.
  3. Terraform Enterprise now supports a new Flexible deployment option. Terraform Enterprise can now be deployed to Red Hat OpenShift. The feature is still in Beta stage. To get started, please read the updated Kubernetes and OpenShift requirements and check out Operater Terraform Enterprise on Red Hat OpenShift.

Features

  1. You can now search for organizations by name on the main organizations page.
  2. A new page has been added to allow administrators to view and cancel the current run for each workspace in an organization. For more information, refer to Organizations.

Improvements

  1. An organization owner can now leave an organization if that organization has other active owners.
  2. The sentinel worker has been updated to 0.26.0.

Bug Fixes

  1. The tfe.run.limit metric is now displayed in the JSON representation of metrics.
  2. When a workspace is deleted, it will not longer appear in the variable set page.
  3. Attaching a VCS provider to a project using the attach to a project endpoint will no longer inadvertently remove existing projects attached to the same provider.
  4. When you edit a workspace variable and wait for some time before clicking the Cancel button, the variable now reverts back to its original key and value.
  5. Managing a run task with too many workspace associations could time out and display an error, preventing any updates to that run task. The number of workspace associations is now checked before loading, and will only display the workspaces if there are fewer than 50.

Security

  1. Container and binary updates address reported vulnerabilities (CVEs) in underlying base images, packages, and dependencies.