use .terraform-version

This commit is contained in:
Victor Martinez 2024-12-11 21:32:18 +01:00
parent c7f7145902
commit 149638b372
No known key found for this signature in database
GPG key ID: 3EF267DA33D65715
3 changed files with 89 additions and 6 deletions

View file

@ -260,7 +260,7 @@ The action supports the following inputs:
for available range specifications). Examples are: `"<1.2.0"`, `"~1.1.0"`, `"1.1.7"` (all three installing
the latest available `1.1` version). Prerelease versions can be specified and a range will stay within the
given tag such as `beta` or `rc`. If no version is given, it will default to `latest`.
- `terraform_version_file` - (optional) The path to a file containing terraform version. Supported file types are `.tool-versions` or anything else. See more details in [about version-file](#Terraform-version-file).
- `terraform_version_file` - (optional) The path to a file containing terraform version. Supported file types are `.tool-versions` or `.terraform-version`. See more details in [about version-file](#Terraform-version-file).
- `terraform_wrapper` - (optional) Whether to install a wrapper to wrap subsequent calls of
the `terraform` binary and expose its STDOUT, STDERR, and exit code as outputs
named `stdout`, `stderr`, and `exitcode` respectively. Defaults to `true`.
@ -269,7 +269,7 @@ The action supports the following inputs:
If the `terraform_version_file` input is specified, the action will extract the version from the file and install it.
Supported files names are `.tool-versions` or anything else.
Supported files names are `.tool-versions` or `.terraform-version`.
In `.tool-versions` file, terraform version should be preceded by the terraform keyword (e.g., `terraform 1.13.0`).
The `.tool-versions` file supports version specifications in accordance with Semantic Versioning ([semver](https://semver.org/)) and [Semver Ranges](https://www.npmjs.com/package/semver#ranges).
In other files, the version should be specified as explainied in the `terraform_version` input.