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

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

Terraform Enterprise v202212-2 (667)

Last required release: v202207-2 (642)

Changes Since v202212-1

  1. The logging for some services (tfe-atlas and tfe-sidekiq) are set to debug causing an increase in logging output. This is corrected in v202301-2.

  2. The Certificate Authority (CA) bundle is now injected into the tfe-task-worker container, fixing an issue where Sentinel policies would return x509 errors when connecting to HTTPS endpoints.

Deprecations

The following operating systems are deprecated, and Terraform Enterprise will stop supporting them following the February 2023 release (v202302-1).

  • Debian 8, 9
  • Ubuntu 14.04, 16.04
  • Amazon Linux 2014.03, 2014.09, 2015.03, 2015.09, 2016.03, 2016.09, 2017.03, 2017.09, 2018.03

The following PostgreSQL server versions are deprecated, and Terraform Enterprise will stop supporting them following the February 2023 release (v202302-1).

  • PostgreSQL 11

Highlights

  1. The tfe-nomad container has been removed and replaced with a new tfe-task-worker container. The tfe-task-worker container is now responsible for running sentinel, cost-estimation, and plan-exporter tasks. Logs for these tasks can now be found in the tfe-task-worker container logs. This change is part of a larger effort to refresh the architecture of Terraform Enterprise, improve performance and reliability of runs, and support future application-level features.
  2. A new tfe-atlas-ui container has been added to serve the Terraform Enterprise frontend and static assets.
  3. Terraform Enterprise no longer starts when connected to an unsupported PostgreSQL server version to prevent potential database incompatibility issues when upgrading. The entry PostgreSQL version X does not meet PostgreSQL version requirements will appear in the logs.
  4. Terraform Enterprise now supports Run tasks in the Pre-plan and Pre-apply stages of a run. Run tasks are custom integrations that can send run data to external services. They can either produce warnings or stop runs, depending on your workspace settings.

Features

  1. For Terraform versions 1.2+, Terraform Enterprise hides data sources reads in the plan UI by default. Use the filter checkbox to show them when necessary.
  2. The List Workspaces API endpoint now supports wildcard matching. For example, searching with search[wildcard-name]=*-prod returns all workspaces ending in -prod.

Improvements

  1. Improved the performance of a data migration added in Terraform Enterprise v202207-1 for installations with large amounts of configuration versions.
  2. You no longer need to confirm plans with no infrastructure changes that Terraform created with the allow-empty-apply option. You may want to use this option when you upgrade your workspace's state to a new Terraform version.
  3. The users administration page now displays a warning next to accounts with an unconfirmed email address.

Bug Fixes

  1. Terraform Enterprise no longer occasionally fails to save outputs associated with a new state.
  2. The tfe-registry-worker now consistently cleans up the temp disk space that it used during module ingress.
  3. Using the the API to create a module version beginning with v no longer prevents the registry from displaying other module versions. Versions like v1.0.3 previously caused failures.
  4. You can now download Sentinel mocks for older Terraform runs.
  5. When you cancel a Terraform run during the apply process, Terraform Enterprise now displays the resource state as Unknown. Previously, the UI showed a message incorrectly implying that Terraform was still attempting to complete the apply.
  6. The VCS provider settings no longer displays a blank page for organizations with large numbers of VCS providers.
  7. Failed attempts to reauthorize VCS providers no longer prevent new reauthorization workflows.
  8. OAuth clients that the tfe-provider is managing can no longer start VCS provider reauthorization.
  9. Public GitHub avatars will no longer be used for private provider logos when the namespace for the private provider matches a GitHub username.

Security

  1. Container updates address reported vulnerabilities (CVEs) in underlying packages and dependencies.