terraform-version

terraform-version action

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 a Terraform 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:

1. The version set in the Terraform Cloud/Enterprise workspace if the module uses a remote backend or cloud configuration, and the remote workspace exists.
2. A required_version constraint in the terraform configuration. If the constraint is range, the latest matching version is used.
3. A tfswitch .tfswitchrc file in the module path
4. A tfenv .terraform-version file in the module path
5. An asdf .tool-versions file in the module path or any parent path
6. A TERRAFORM_VERSION environment variable containing a version constraint. If the constraint allows multiple versions, the latest matching version is used.
7. The Terraform version that created the current state file (best effort).
8. 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.

Inputs

• path

  Path to the terraform root module

  • Type: string
  • Optional
  • Default: The action workspace

• workspace

  The workspace to determine the Terraform version for.

  • Type: string
  • Optional
  • Default: default

• backend_config

  List of terraform backend config values, one per line.

  This will be used to fetch the Terraform version set in the TFC/TFE workspace if using the remote backend. 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_file

  List 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 TFC/TFE workspace if using the remote backend. 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

Environment Variables

• TERRAFORM_CLOUD_TOKENS

  API tokens for terraform cloud hosts, of the form <host>=<token>. Multiple tokens may be specified, one per line. These tokens may be used for fetching required modules from the registry, and determining the terraform version set in the remote workspace.

  e.g for terraform cloud:

  env:
    TERRAFORM_CLOUD_TOKENS: app.terraform.io=${{ secrets.TF_CLOUD_TOKEN }}

  With Terraform Enterprise or 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_KEY

  A SSH private key that terraform will use to fetch git module sources.

  This should be in PEM format.

  For example:

  env:
    TERRAFORM_SSH_KEY: ${{ secrets.TERRAFORM_SSH_KEY }}

  • Type: string
  • Optional

• TERRAFORM_PRE_RUN

  A 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:bullseye, with the command run using bash -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

• TERRAFORM_HTTP_CREDENTIALS

  Credentials 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 by http:// & 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

Outputs

• terraform

  The terraform version that is used by the terraform configuration

• 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 random output will be created with the value 2.2.0.

Example usage

on: [push]

jobs:
  required_version:
    runs-on: ubuntu-latest
    name: Print the required terraform  and provider versions
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Test terraform-version
        uses: dflook/terraform-version@v1
        id: terraform-version
        with:
          path: my-configuration

      - name: Print the version
        run: echo "The terraform version was ${{ steps.terraform-version.outputs.terraform }}"
        
      - name: Print aws provider version
        run: echo "The aws provider version was ${{ steps.terraform-version.outputs.aws }}"