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

[Bug]: Installation Error: Unsupported Terraform Core version (v1.4) #394

Closed
jtanton opened this issue Mar 17, 2023 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@jtanton
Copy link

jtanton commented Mar 17, 2023

Installation method

Own AWS account

What happened?

New minor issue. I am now on ubuntu (WSL) and my Terraform version is 1.4. The required version statement won't let me leave version 1.3.x so I have to change the TF code. Should I do a pull request to fix this or can you update the TF in the repo?
│ Error: Unsupported Terraform Core version

│ on modules/ide/main.tf line 10, in terraform:
│ 10: required_version = "~> 1.3.7" (edited)

1:06
on main.tf line 9, in terraform:
│ 9: required_version = "> 1.3.7"
1:06
on modules/cluster/providers.tf line 43, in terraform:
│ 43: required_version = "
> 1.3.7"

What did you expect to happen?

I expected Terraform Version 1.37 + to work per documetation. I am running V1.4

How can we reproduce it?

Yes

Anything else we need to know?

I removed the tilde ~ in my local files and now INIT is running.

EKS version

lab default version

@jtanton jtanton added the bug Something isn't working label Mar 17, 2023
@bryantbiggs
Copy link
Member

bryantbiggs commented Mar 19, 2023

the ~> pattern will allow the rightmost version to "float" and automatically update to the latest version available. The current form allows for versions 1.3.7, 1.3.8, etc. up to, but not including, 1.4.0 (can achieve same outcome using the pattern ">= 1.3.7, <1.4.0". The fix here would be to remove the patch restriction (i.e. - "~> 1.3"); this is preferred over the >= 1.3.7 form because this form would allow something like 2.0 if that were to be released in the future but "~> 1.3" would not

@niallthomson
Copy link
Contributor

This will have been resolved by the new workshop structure just published since we pin the TF CLI version installed in Cloud9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants