This is one of a suite of Terraform related actions - find them at dflook/terraform-github-actions.
This action determines the Terraform and provider versions to use for the root module.
The best way to specify the version is using a required_version constraint.
The version to use is discovered from the first of:
- The version set in the cloud workspace if the module uses a
remotebackend orcloudconfiguration, and the remote workspace exists. - A
required_versionconstraint in the Terraform configuration. If the constraint is range, the latest matching version is used. - A tfswitch
.tfswitchrcfile in the module path - A tfenv
.terraform-versionfile in the module path - An asdf
.tool-versionsfile in the module path or any parent path - A
TERRAFORM_VERSIONenvironment variable containing a version constraint. If the constraint allows multiple versions, the latest matching version is used. - The Terraform version that created the current state file (best effort).
- The latest Terraform version
The version of Terraform and all required providers will be output to the workflow log.
Other terraform actions automatically determine the Terraform version in the same way. You only need to run this action if you want to use the outputs yourself.
-
pathThe path to the Terraform root module directory.
- Type: string
- Optional
- Default: The action workspace
-
workspaceThe workspace to determine the Terraform version for.
- Type: string
- Optional
- Default:
default
-
backend_configList of Terraform backend config values, one per line.
This will be used to fetch the Terraform version set in the cloud workspace if using the
remotebackend. For other backend types, this is used to fetch the version that most recently wrote to the Terraform state.with: backend_config: token=${{ secrets.BACKEND_TOKEN }}
- Type: string
- Optional
-
backend_config_fileList of Terraform backend config files to use, one per line. Paths should be relative to the GitHub Actions workspace
This will be used to fetch the Terraform version set in the cloud workspace if using the
remotebackend. For other backend types, this is used to fetch the version that most recently wrote to the Terraform state.with: backend_config_file: prod.backend.tfvars
- Type: string
- Optional
-
terraformThe Hashicorp Terraform or OpenTofu version that is used by the configuration.
- Type: string
-
tofuIf the action chose a version of OpenTofu, this will be set to the version that is used by the configuration.
- Type: string
-
Provider Versions
Additional outputs are added with the version of each provider that is used by the Terraform configuration. For example, if the random provider is used:
provider "random" { version = "2.2.0" }
A
randomoutput will be created with the value2.2.0.- Type: string
-
GITHUB_DOT_COM_TOKENThis is used to specify a token for GitHub.com when the action is running on a GitHub Enterprise instance. This is only used for downloading OpenTofu binaries from GitHub.com. If this is not set, an unauthenticated request will be made to GitHub.com to download the binary, which may be rate limited.
- Type: string
- Optional
-
TERRAFORM_CLOUD_TOKENSAPI tokens for cloud hosts, of the form
<host>=<token>. Multiple tokens may be specified, one per line. These tokens may be used with theremotebackend and for fetching required modules from the registry.e.g:
env: TERRAFORM_CLOUD_TOKENS: app.terraform.io=${{ secrets.TF_CLOUD_TOKEN }}
With other registries:
env: TERRAFORM_CLOUD_TOKENS: | app.terraform.io=${{ secrets.TF_CLOUD_TOKEN }} terraform.example.com=${{ secrets.TF_REGISTRY_TOKEN }}
- Type: string
- Optional
-
TERRAFORM_SSH_KEYA SSH private key that Terraform will use to fetch git/mercurial module sources.
This should be in PEM format.
For example:
env: TERRAFORM_SSH_KEY: ${{ secrets.TERRAFORM_SSH_KEY }}
- Type: string
- Optional
-
TERRAFORM_HTTP_CREDENTIALSCredentials that will be used for fetching modules sources with
git::http://,git::https://,http://&https://schemes.Credentials have the format
<host>=<username>:<password>. Multiple credentials may be specified, one per line.Each credential is evaluated in order, and the first matching credentials are used.
Credentials that are used by git (
git::http://,git::https://) allow a path after the hostname. Paths are ignored byhttp://&https://schemes. For git module sources, a credential matches if each mentioned path segment is an exact match.For example:
env: TERRAFORM_HTTP_CREDENTIALS: | example.com=dflook:${{ secrets.HTTPS_PASSWORD }} github.com/dflook/terraform-github-actions.git=dflook-actions:${{ secrets.ACTIONS_PAT }} github.com/dflook=dflook:${{ secrets.DFLOOK_PAT }} github.com=graham:${{ secrets.GITHUB_PAT }}
- Type: string
- Optional
-
TERRAFORM_PRE_RUNA set of commands that will be ran prior to
terraform init. This can be used to customise the environment before running Terraform.The runtime environment for these actions is subject to change in minor version releases. If using this environment variable, specify the minor version of the action to use.
The runtime image is currently based on
debian:bookworm, with the command run usingbash -xeo pipefail.For example:
env: TERRAFORM_PRE_RUN: | # Install latest Azure CLI curl -skL https://aka.ms/InstallAzureCLIDeb | bash # Install postgres client apt-get install -y --no-install-recommends postgresql-client
- Type: string
- Optional
on: [push]
jobs:
required_version:
runs-on: ubuntu-latest
name: Print the required Terraform and provider versions
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Test terraform-version
uses: dflook/terraform-version@v2
id: terraform-version
with:
path: my-configuration
- name: Print the version
run: echo "The version was ${{ steps.terraform-version.outputs.terraform }}"
- name: Print aws provider version
run: echo "The aws provider version was ${{ steps.terraform-version.outputs.aws }}"