Nothing works after update to 2.x

[dac73]

It's kinda unusable now, and install another version returns 404

😞

Currently looks like extension doesn't support configuration with multiple environments configs with subfolders, and if I open "project" from env folder then all referenced modules don't work.
My setup (that was working until now):

.
├── env
│   ├── staging-dev
│   │   ├── main.tf
│   │   └── variables.tf
│   └── staging-qa
│       ├── main.tf
│       └── variables.tf
├── modules
│   ├── some_module
│   │   ├── main.tf
│   │   ├── outputs.tf
│   │   └── variables.tf
└── README.md

[dac73]

To install working version: #381 (comment)

[3mard]

Same here, very frustrating

[brandonh-msft]

.tf file formatting also busted.

[chriswacker]

I share your frustration. I had to install 1.4 with the .vsix and am still working with 0.11 syntax. At least that way you get some more advanced autocomplete, and even supports multiple configurations in sub-directories (which last I heard has no plans for support in 2.0).

As long as you open a single, initialized configuration, you get the listed features, which are only:

• Manages installation and updates of the Terraform Language Server (terraform-ls), exposing its features:
  • Initialized provider completion (resource names, data source names, attribute names)
• Includes syntax highlighting for .tf and .tfvars files (and .hcl) -- including all syntax changes new to Terraform 0.12
• Closes braces and quotes
• Includes for_each and variable syntax shortcuts (fore, vare, varm)

But even some of these are kinda broken.

[dac73]

Well if that is true, I hope some one will fork 1.4 and continue from there. 1.4 work wonders for 0.12 2.x is huge disappointment in current state.

…

On Fri, 12 Jun 2020, 19:26 chriswacker, ***@***.***> wrote: I share your frustration. I had to install 1.4 with the .vsix and am still working with 0.11 syntax. At least that way you get some more advanced autocomplete, and even supports multiple configurations in sub-directories (which last I heard has no plans for support in 2.0). As long as you open a single, initialized configuration, you get the listed features, which are only: - Manages installation and updates of the Terraform Language Server (terraform-ls), exposing its features: - Initialized provider completion (resource names, data source names, attribute names) - Includes syntax highlighting for .tf and .tfvars files (and .hcl) -- including all syntax changes new to Terraform 0.12 - Closes braces and quotes - Includes for_each and variable syntax shortcuts (fore, vare, varm) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE53IY5EH3GTOLJR6MR4TETRWJQMJANCNFSM4N4GUEPA> .

[rpstreef]

I have a similar setup as the OP, this version completely breaks and is unusable.

[jianzhiteh]

Auto formatting doesn't work anymore... "There is no formatter for 'terraform' files installed."

[ghost]

No formating, no linting, no code suggestions.

[darrenfurr]

Ran into the same problem...workaround:

• Remove 2.0.1 extension from VS Code
• Download 1.4.0 of the vsix from here: https://github.com/hashicorp/vscode-terraform/releases/download/v1.4.0/mauve.terraform-v1.4.0.vsix
• Manually install it: code --install-extension mauve.terraform-v1.4.0.vsix
• Restart VS Code
• When prompted install language server: v.0.0.11-beta2

All the formatting is back & everything is happy again.

[paultyng]

Here are the canonical tracking issues for things raised in this thread:

• 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

Until the VS Code issue is resolved, you can manually downgrade following these instructions: https://github.com/hashicorp/vscode-terraform/wiki/Install-a-Pre-transfer-Version

[vikassood1]

Ran into the same problem...workaround:

• Remove 2.0.1 extension from VS Code
• Download 1.4.0 of the vsix from here: https://github.com/hashicorp/vscode-terraform/releases/download/v1.4.0/mauve.terraform-v1.4.0.vsix
• Manually install it: code --install-extension mauve.terraform-v1.4.0.vsix
• Restart VS Code
• When prompted install language server: v.0.0.11-beta2

All the formatting is back & everything is happy again.

Thank you so very much. Good to know I am not the only one losing my mind

[ghost]

@paultyng

The formatting does not work at all, not only when there is a missing initialization. And what is about code suggestions? In which Ticket it will be solved? Sorry for asking, but i dont see that and i alredy asked in another issue where this is not been answered.

[paultyng]

@feeyu7 I think both of those issues are related to the different folder structure issue (hashicorp/terraform-ls#32). We are working to support multiple different root and nested module configurations (including allowing users to just specify the one they want to use). So even if initialized, the root module detection is not finding the appropriate directory so causing it problems.

[chelnak]

Ran into the same problem...workaround:

• Remove 2.0.1 extension from VS Code
• Download 1.4.0 of the vsix from here: https://github.com/hashicorp/vscode-terraform/releases/download/v1.4.0/mauve.terraform-v1.4.0.vsix
• Manually install it: code --install-extension mauve.terraform-v1.4.0.vsix
• Restart VS Code
• When prompted install language server: v.0.0.11-beta2

All the formatting is back & everything is happy again.

Thank you!

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