Describe the bug
The ubuntu-latest runner has been updated with Terraform v0.13.0. This is a breaking change. Furthermore, the docs at Ubuntu1804-README.md have not been updated to reflect this.
Area for Triage:
Question, Bug, or Feature?:
Bug
Virtual environments affected
Expected behavior
One of:
ubuntu-latestActual behavior
GitHub workflows which rely on Terraform v0.12.29 fail without updates.
Hello @elliotchaim,
Thank you for the reported issue.
We always install the latest version of tools into images. Terraform was updated in the scope of the newest ubuntu release. You can track deployment status using the following link.
The documentation will be updated upon completion of the deployment.
I suggest to use official setup-terraform action to freeze specific version: https://github.com/marketplace/actions/hashicorp-setup-terraform
Thanks for the info @Darleev
@maxim-lobanov That looks like a very good idea, thank you.
@elliotchaim I'm going to close the issue.
In case of any questions, do not hesitate to contact us.
@Darleev -
As @elliotchaim mentioned, v0.13 is _incompatible_ with v0.12 - Terraform is still in v0 stage, and their minor changes are breaking. This change broke things for us too. IMHO, such things are not acceptable for mature "CI as a service" provider. Please consider reopening, or at the very least update documentation.
@khitrenovich
@maxim-lobanov provided good steps to mitigate the issue.
Deployment is underway and you can track status here. The documentation will be updated as soon as the build is complete( Link to PR ).
Is it possible to somehow reference a previous image using 20200806.0 ?
Is it possible to somehow reference a previous image using
20200806.0?
Suggestion above by @maxim-lobanov worked perfectly for us, and it will protect you from similar changes in the future.
Most helpful comment
@Darleev -
As @elliotchaim mentioned,
v0.13is _incompatible_ withv0.12- Terraform is still inv0stage, and their minor changes are breaking. This change broke things for us too. IMHO, such things are not acceptable for mature "CI as a service" provider. Please consider reopening, or at the very least update documentation.