-
Notifications
You must be signed in to change notification settings - Fork 131
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
unknown block type: "terraform" (terraform 0.13 unsupported?) #280
Comments
Hi @kevincantu There are differences between Terraform core versions (in terms of schema/syntax), which will need to be reflected in the underlying HCL decoder. For now we only support the essential blocks which don't differ between versions and for which we have schema (by obtaining it from providers) - which is terraform-ls/internal/terraform/lang/parser.go Lines 101 to 115 in 565d9c1
Supporting other blocks, such as the |
Version The only part of the block that is not completable yet is the body of the VS Code should automatically update LS to the latest version on the next launch, or if you restart it. With that in mind I'm going to close this issue. |
Awesome! 🐬 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
So I'm upgrading to 0.13 just as I've changed editors to VS Code and installed this extension... And I see somewhat limited functionality. While working out other adjustments to settings I've discovered this in the Output tab, that's somewhat startling:
Part of my
~/Library/Application Support/Code/User/settings.json
:The output of the tab in the console corresponding to terraform-ls: that repo:
It seems to have a problem with my
backend.tf
:Which can, with 0.13, be init / plan / applied without objections.
Formatting on save works!
But what i expect is that schema errors should be detected and displayed. Actually, however, they're not!
I can change that to
required_providersxxxxx
and save the file and see no problems in VS Code, when aterraform plan
reveals:So something is wrong.
The text was updated successfully, but these errors were encountered: