Terraform Enterprise 2.0.3 is available

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

Some key highlights and important bits from the release notes:

Bug Fixes

  1. Readiness checks now behave correctly when a node is draining. In previous releases, readiness checks returned an HTTP 503 status during node drain, which could cause load balancers in some non‑Kubernetes environments to remove draining nodes from service unintentionally. This issue has been resolved, and readiness checks now return a successful HTTP 200 response while indicating the draining state so nodes are handled appropriately during upgrades.

  2. Terraform Enterprise now supports PostgreSQL extensions installed in non-default schemas. Previously, Terraform Enterprise could fail to start or operate correctly in environments where PostgreSQL extensions are installed in database-managed schemas, leading to initialization errors. This release introduces new configuration option (TFE_DATABASE_EXTRA_SCHEMAS) that let you include additional schemas in the connection search_path, enabling compatibility with PostgreSQL environments that restrict default permissions.

  3. Terraform Enterprise now supports deployments with pre-provisioned PostgreSQL schemas without requiring database-level CREATE permissions. Previously, startup checks required database-level CREATE privileges even when all required Terraform Enterprise schemas already existed, which could prevent deployments in DBA-managed PostgreSQL environments. This update improves the validation logic to check for existing schemas and verify appropriate permissions at the schema level, allowing Terraform Enterprise to start successfully in these environments.

  4. Terraform Enterprise now handles deployments with long or complex hostnames reliably. Previously, Terraform Enterprise could fail to start in environments with long hostnames due to Nginx limitations when building the server names hash. This issue has been resolved by increasing the supported hash bucket size, preventing startup failures.

  5. You can now allow Terraform Enterprise to start even if expired certificates are present in the CA bundle. Previously, Terraform Enterprise failed to start if any expired certificates were detected in the CA certificate bundle, which could delay restarts in environments where certificate management is handled externally. This release introduces the TFE_STARTUP_CHECKS_IGNORE_FAILURES configuration option, allowing you to treat these checks as warnings instead of blocking startup.

  6. Explorer now includes remote modules, such as those sourced from GitHub. Previously, modules sourced directly from version control were not shown in Explorer, limiting visibility into module usage across your organization. This update ensures non‑registry modules are included, giving you a more complete view of the modules used in your Terraform Enterprise deployment.

Security

  1. Security vulnerabilities have been addressed and resolved in this update to enhance overall system protection.