James Pogran

If you have some time, we recently did a live stream about what we've delivered over the last few months. Hopefully some of it is useful to you youtu.be/hYBWFg8C1ZY

ICYMI: We just finished a live demo of some of the awesome stuff in the @HashiCorp Terraform @code extension. Intellisense, go to definition and more without terraform init! #terraform youtube.com/watch?v=hYBWFg8C…

Come by and talk @code and @HashiCorp Terraform and say hi!

We do currently provide that for providers, module and backend blocks. Resource blocks will be handled when github.com/hashicorp/terrafo… lands

NBD, just @HashiCorp in @code on github.dev

Well the day can only go up from here. A bird pooped on my phone while I was holding it.

We're working on it! Unfortunately it's a non-trivial problem. There are many ways to organize Terraform code and many ways to open it in vs code, all valid. Do you mind opening an issue with how you do yours and we can work on how to help?

Actually I got myself confused. You are correct it’s supposed to be # for tf files. We recently released a pure HCL extension for VS Code which made me anxious I thought I broke something for you. That being said, let me know if there’s anything we can do better in the extension

Let me know why over at github.com/hashicorp/vscode-… and we’ll fix it

@tefields @shanselman

Thanks for the info! It sounds like some of this would be found by 'terraform validate', but not all of it. You can have the extension run it using the command palette or you can configure it to run on save:

Hey 👋 I work on that extension. I’d love to hear what’s not working for you. We’ve shipped a lot these past few months and have some new features on the horizon to make things easier to use, but we know there are some rough edges