-
Notifications
You must be signed in to change notification settings - Fork 188
Description
Extension Version
2.37.5
VS Code Version
Version: 1.105.1 (Universal)
Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0
Operating System
macOS 15.7.1 (24G231)
Terraform Version
Terraform v1.13.4 on darwin_arm64
Steps to Reproduce
- Install mise
- Clone this mise-vscode fork
- Run
mise installandmise run devto open vscode with the extension running - Install the HashiCorp Terraform extension
- Open the attached gist
Expected Behavior
The terraform.languageServer.terraform.path property should be configured correctly by the mise-vscode extension, pointing to the terraform binary installed by mise. Code formatting should run.
Actual Behavior
The mise-vscode extension fails to configure the terraform.languageServer.terraform.path property at the workspace level with the following error:
[error] Failed to configure the extension hashicorp.terraform for terraform: CodeExpectedError: Unable to write terraform.languageServer.terraform.path to Workspace Settings. This setting can be written only into User settings.
Gist
https://gist.github.com/asmeikal/b312ab0cddc3886b4e5d9cacfccc6059
Anything Else?
I'm managing the terraform version using mise, and I'm trying to add support for the hashicorp.terraform extension to the mise-vscode extension, which sets appropriate executable paths for specific extensions to the executables installed by mise. The PR in the "References" section restricted the terraform.languageServer.terraform.path from the machine-overridable scope to the machine scope, preventing the mise-vscode extension from working, which is too restrictive for some configurations, and the issue in the "References" section seems to rely on the assumption that there is a single terraform executable per machine.
Workarounds
No response
References
- Set machine scope to path settings #1187
- Flag machine specific configurations like paths as machine scoped #187
Help Wanted
- I'm interested in contributing a fix myself
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment