Terraform Enterprise 2.0.2 is available

Terraform HCP Terraform
, ,
1

The Terraform Enterprise team would like to announce the release 2.0.2 is now available.

Some key highlights and important bits from the release notes:

Known Issues

  1. When a Terraform Enterprise node enters a draining state, readiness checks return an HTTP 503 status. In some non‑Kubernetes cloud environments, checks for load balancers may interpret this as an unhealthy node and remove it from service, even though the node is intentionally draining and not accepting new requests. When draining nodes in your Terraform Enterprise installation, consider disabling readiness checks and instead use host-level health signals. For example, you can enable Auto Scaling Group instance checks in AWS, disable auto-repair in AWS, or disable auto-healing policies in GCP. This issue does not affect Terraform Enterprise deployments on Kubernetes or OpenShift.

Bug Fixes

  1. Policy evaluations could fail to complete in some cases, particularly in workspaces with a large number of configured policies, causing runs to remain in progress. This issue has been resolved, and policy checks now execute and complete as expected. If you applied the workaround described in the support knowledge base article (Runs Stuck Checking Sentinel Policies and 503 Errors on /api/v1/health/readiness in Terraform Enterprise), you can re‑enable policy checks and evaluations in your workspaces.
  2. Product usage reports were not created successfully, which prevented usage reports from receiving up‑to‑date data. This issue has been resolved.
  3. The Diagnostics API returned an HTTP 503 status for the task worker due to insufficient Kubernetes API permissions required by the diagnostics check. This resulted in a false unhealthy status being shown in the Terraform Enterprise. This issue has been resolved, and the Diagnostics API now reflects the actual availability of the task worker.
  4. Explorer now includes remote (non-registry) modules, such as those sourced from GitHub.