Impossible to update to a newer terraform version if only the GitHub Action is allowed to execute terraform #335
Comments
|
Hello, thanks for creating an issue. The version in the Number 1 in the version discovery list relates to Terraform Cloud/Enterprise workspaces, where the remote workspace version always takes priority. This log shows the version coming from a local |
|
I think number 1 is inspecting my S3 remote state? Here is provider "aws" {
region = var.region
profile = "robmoss"
default_tags {
tags = {
Owner = var.owner
purpose = var.purpose
Name = "${var.owner}: ${var.purpose}"
map-migrated = "d-server-001j25bgmzlvy7"
}
}
}
provider "tls" {}
provider "http" {}There is no |
|
I updated the original issue to contain debug-enabled logs. |
|
Hold on a minute. I've uploaded the log from the wrong run. Updating again - sorry! Edited: updated with the stuff from the correct repo. From the logs, my assumption was wrong and my PR is useless. |
|
OK, here it is. I have this:
According to the documentation, I should have this:
However, |
|
That's a good find, I didn't know Terraform allowed that. |
|
I didn't know Terraform wasn't supposed to allow anything else! |
|
Version 1.42.1 has been released that allows a |
Problem description
In the documentation, it specifies the following first two points for
terraform-version:required_versionconstraint in the Terraform configuration. If the constraint is range, the latest matching version is used.We aren't allowed to execute terraform locally, as there are loads of validation steps to prevent people from breaking things that run in the GitHub Actions. Therefore, if my last terraform apply was on version
1.7.5and I've validated I can switch to1.8.0, the only way I can do that is to change my required_version to==1.8.0. Butterraform-versionignores this when installing terraform, installing version1.7.5, and then it barfs because terraform1.7.5won't apply whenrequired_versionis set to==1.8.0.Suggested fix:
required_versionoverrides the version in the state file if it's newer.Terraform version
1.8.0
Backend
s3
Workflow YAML
Workflow log
Has debug logging been enabled?
ACTIONS_STEP_DEBUGsecret was set totruewhen capturing the workflow log above.The text was updated successfully, but these errors were encountered: