Issues in 2.x release

[ppanyukov]

Everything was working fine. Now the extension auto-updated and nothing works. Who make this assumption that the root of my directory is terraform thing? Why can't I disable this "language server"? Formatter doesn't work either. Can't revert to previous working version either.

Total disaster.

[oliversalzburg]

See #366 (comment) for a possible workaround.

[sorin-costea]

I'm a bit confused, what does this 2.0.1 version actually DO, I mean part from installing without errors?

[oliversalzburg]

@sorin-costea I believe one of the important changes is the improved 0.12 language syntax support.

In the previous version, my entire project file tree was marked red, because VS Code thought every single file had syntax errors. I don't have that anymore, which is nice.

[sorin-costea]

@oliversalzburg you're right, there are no syntax errors marked anymore - because it does nothing 😊 No linting is happening at all just a bit of coloring, and you'll see your errors only when terraform plan...

[FernandoMiguel]

@sorin-costea I believe one of the important changes is the improved 0.12 language syntax support.

In the previous version, my entire project file tree was marked red, because VS Code thought every single file had syntax errors. I don't have that anymore, which is nice.

@oliversalzburg
the never officially released v1.4 did all that with 0.12 , no issues.
but since it was stuck in a thread on github , not everyone knew about it.

[oliversalzburg]

@oliversalzburg you're right, there are no syntax errors marked anymore - because it does nothing 😊 No linting is happening at all just a bit of coloring, and you'll see your errors only when terraform plan...

Yeah, that surely is disappointing. For me the root cause was that I have multiple Terraform projects in my workspace and the extension recognized that as an uninitialized workspace. The comment I quoted above helped me to work around the issue. Now I'm at least able to work again.

There was actually an RC of the 2.0 version of this extension, which I neglected to test :( Now I'm just hoping for quick improvements. Good luck :)

[sorin-costea]

@FernandoMiguel I uninstalled 2.0.1 and installed 1.4 from the download file and it still does no linting. Could it be something to be configured on MY side? I never did anything for the 1.3.x they just worked fine (except 0.12 syntax) after install...

[paultyng]

@ppanyukov I understand the frustration, we are working to address the outstanding issues, all that said there is no need for the sarcasm and doesn't help the situation or get it fixed any faster.

The downgrading issue is still an upstream VS Code issue. It was just (very) unfortunate timing that they had that bug introduced when we shipped our new version. We never intended that to stop working which is why our release notes and launch blog post both included the standard downgrade instructions.

[FernandoMiguel]

@FernandoMiguel I uninstalled 2.0.1 and installed 1.4 from the download file and it still does no linting. Could it be something to be configured on MY side? I never did anything for the 1.3.x they just worked fine (except 0.12 syntax) after install...

you need tflint (app and vscode ext https://github.com/terraform-linters/tflint )
I opened ticket #337 for that

[paultyng]

I don't think there is anything new raised in this issue, the existing ones probably cover it:

• Different folder structures: Support single files and parent (non-Terraform) folders terraform-ls#32
• Formatting without initialization: Formatting should work regardless of workspace/initialization state terraform-ls#165
• Diagnostic support (red squiggles): Validate configuration and publish diagnostics terraform-ls#27
• VS Code downgrade issue: "Server returned 404" when trying to install different versions of extensions in VS Code microsoft/vscode#99699

[ghost]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.