Error thrown when saving .tf or .tfvars files with names beginning with a dot

[chriswacker]

Versions

Extension

v2.23.0

VS Code

1.68.1

Operating System

Linux a15830e0f40b 5.10.16.3-microsoft-standard-WSL2 hashicorp/vscode-terraform#1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 GNU/Linux

Terraform Version

Terraform v1.1.5
on linux_amd64

Steps To Reproduce

1. Create a file with name: .example.tf (needs to start with a dot and be a .tf or .tfvars file)
2. Open the file and save it
3. See error

Expected Behavior

No error

Actual Behavior

Received error from extension:

Unable to update "/path/to/file/.example.tf": filetype not supported. This is likely a bug which should be reported.

[radeksimko]

Hi @chriswacker
Thanks for the report. I believe this is a duplicate of #957 which is being fixed in #968

[radeksimko]

Actually the mentioned issue/PR handles tfvars, but I think .*.tf files still need a solution.

@chriswacker I'm curious what's your use case for *.tf files with dot at the beginning, since Terraform ignores these files?

The reason I'm asking is because it's an edge case we'll have to account for somehow. We could treat it as if it's not ignored, but that means, that e.g. if there are any errors in parsing, duplicates and any other diagnostics they'll all come up for the whole module, which doesn't reflect the reality - as invalid hidden files don't really prevent you from applying or planning.

I think what would make more sense is to apply the same logic we apply to autoloaded vs individual tfvars files. i.e. *.auto.tfvars vs foobar.tfvars where any diagnostics for foobar.tfvars are only visible when that individual file is open and *.auto.tfvars diagnostics are always visible.

[chriswacker]

Hey @radeksimko, my use case is only for .*.tfvars files. In my own troubleshooting I noticed the error occurred for .*.tf files as well, and since I wasn't aware that terraform ignored those files, I thought I'd include that in this issue.

Glad a fix is on the way!

[github-actions]

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 details necessary to investigate further.