Skip to content
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

Open
2 of 15 tasks
endorama opened this issue Dec 9, 2024 · 3 comments
Open
2 of 15 tasks

Terraform 1.10.0 bug #11136

endorama opened this issue Dec 9, 2024 · 3 comments
Assignees
Labels
awaiting-deployment Code complete; awaiting deployment and/or deployment in progress bug report OS: Ubuntu

Comments

@endorama
Copy link

endorama commented Dec 9, 2024

Description

Terraform v1.10.0 is affected by this bug hashicorp/terraform#36106

Solved 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

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022

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.

@RaviAkshintala
Copy link
Contributor

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.

@patrik-simunic-cz
Copy link

@RaviAkshintala I confirm the presence of this issue, it is affecting all our pipelines that rely on pre-installed Terraform.
It could be worked around by setting up specific version of Terraform (either 1.9.8 or 1.10.1) manually in a dedicated step - but then, that defeats the purpose of having Terraform pre-installed on the runner.
(Yes, it's generally better to do that anyway, but using the pre-installed binary is a tiny bit faster and more convenient.)

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 1.10.0 was released about a week ago.
Is there any chance a new runner image release, with Terraform 1.10.1, will be rolled out in the next 24 hours?

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).

@RaviAkshintala RaviAkshintala added the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label Dec 10, 2024
@RaviAkshintala
Copy link
Contributor

RaviAkshintala commented Dec 10, 2024

Hi @patrik-simunic-cz The latest version of Terraform, 1.10.1, will be included in this week's image rollout. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-deployment Code complete; awaiting deployment and/or deployment in progress bug report OS: Ubuntu
Projects
None yet
Development

No branches or pull requests

3 participants