Skip to main content

Overview

When creating or editing a template, you can specify which version of Infrastructure as Code (IaC) tools to use for your deployments. env zero supports version management for Terraform, OpenTofu, Terragrunt, Pulumi, and Ansible.

Version Resolution Order

When determining which version to use, env zero follows this priority order:
  1. Environment Variables (ENV0_TOOL_VERSION Environment Variable)
  2. Version Files (per-tool repository files such as .terraform-version)
  3. Template Settings (Specified in UI)

Version Specification Methods

1. Environment Variables

You can override the template version setting using environment variables: For Terraform, env zero also accepts ENV0_TF_VERSION as a legacy alias. If both are set, ENV0_TERRAFORM_VERSION takes precedence.

2. Version Files

env zero can automatically detect versions from standard version files located under the directory you configure in the template. If you want to reuse the same version files for multiple folders, set the environment variable ENV0_RESOLVE_FILE_VERSION_RECURSIVELY=true.

3. Template Settings

To associate a specific IaC version with a template:
  1. Open the relevant Template.
  2. Go to the Settings tab and expand Advanced Settings.
  3. Select the desired version from the "Template Type" Version dropdown.
  4. Click Save.
Interface screenshot showing configuration options
Changing a version in an existing template might affect running environments.

Special Version Values

Version from code

For Terraform and OpenTofu, env zero can install a version that the required_version constraint in your code allows. The version dropdown offers Resolve from terraform code - newest allowed and Resolve from terraform code - lowest allowed. OpenTofu templates show opentofu code in place of terraform code. New templates you create in the UI use newest allowed. Existing templates keep their setting until you change it. Newest allowed reads ~> the way Terraform and OpenTofu do, so only the rightmost version number in the constraint can increase:
  • ~> 1.13 allows any 1.x release from 1.13.0, so env zero installs the newest 1.x release.
  • ~> 1.13.0 allows 1.13.x releases only, so env zero installs the newest 1.13 patch.
For Terraform, newest allowed stops at the newest 1.5.x release, the last version env zero supports.
For self-hosted agents: agents older than 4.0.45 install the latest version in place of the newest allowed one.
Terraform Version dropdown with the Resolve from terraform code newest allowed and lowest allowed options

Latest Version

You can specify “latest” for supported IaC tools:
  • Terraform: Latest version up to 1.5.x
  • Pulumi: Latest available version
  • OpenTofu: Latest available version
  • Ansible: Latest available version
The version value for automatic detection is latest.
Terraform versions ≥ 1.6.0 aren’t supportedTerraform versions 1.6.0 and higher are under a BSL license and are not supported in env zero. Consider switching to OpenTofu, the drop-in replacement for Terraform.

Next steps