-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform 1.10.0 bug #11136
Comments
Hi @endorama Thank you for bringing this issue to our attention. We are looking into this issue and will update you on this issue after investigating. |
@RaviAkshintala I confirm the presence of this issue, it is affecting all our pipelines that rely on pre-installed Terraform. I've read that you (GitHub) release a new version of the runner images (with updated packages) more of less once a week. I also see that the last (current) version with Terraform If not, please let us know, so that we can arrange ourselves appropriately (ie. update all the pipelines so they use specific Terraform version and do not rely on the pre-installed binary). |
Hi @patrik-simunic-cz The latest version of Terraform, |
Hi @endorama The latest version of Terraform is included in the Ubuntu 20 and 22 images. Kindly sync the main. We are closing this issue. Thanks. |
Thank you! |
Description
Terraform
v1.10.0
is affected by this bug hashicorp/terraform#36106Solved in
v1.10.1
(PR | release)I expect this issue to be present in all runner images containing Terraform
v1.10.0
, from a quick search the only one affected seems to be Ubuntu 22.04.Platforms affected
Runner images affected
Image version and build link
Version: 20241201.1.0
Is it regression?
no
Expected behavior
Terraform does not have a bug.
Actual behavior
Terraform 1.10.0 included with the image is affected by hashicorp/terraform#36106
Repro steps
Run a GitHub Action pipeline using
terraform apply --auto-approve
with list/dict variables and setting them with env-vars.The text was updated successfully, but these errors were encountered: