-
Notifications
You must be signed in to change notification settings - Fork 180
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
Ignore backend.hcl and .tfilint.hcl #303
Comments
This seems somewhat related to #239 where again the issue seems to be that more general HCL files are being parsed as though they're specifically Terraform modules. |
Hi folks, As for backend configuration, we track support of that in #636 but I would also point out that from v1.1.0 it is possible to configure Terraform Cloud via the new As for tflint support, we intend to integrate via code actions (tracked under #337 and more broadly under #635). As for highlighting For any advanced IntelliSense features (completion, hover, etc.) within tflint config files, we do not intend to provide that as part of the Terraform extension nor Terraform LS, since tflint has its own schema (own keywords in its config files). However we'd be happy for anyone to create a dedicated tflint extension and/or language server, which claims As for building out the language server, we maintain https://github.com/hashicorp/hcl-lang which has still experimental (unstable) API, but is designed to be used to build any HCL2-based language server, such as tflint one. |
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. |
backend.hcl
is used to set up Terraform Cloud..tflint.hcl
is used to configuretflint
.vscode-terraform
currently flags false positive errors in both of these files. Both of these files should be ignored.Below is a valid
backend.hcl
file thatvscode-terraform
is complaining about.Here are similar errors from
.tflint.hcl
.The text was updated successfully, but these errors were encountered: