We use (JSON) objects to group some config options. Where applicable and necessary, we refer to nested fields using the . as a separator. i.e. A hypothetical bar option under {"foo": { "bar": "..." } } would be referred to as foo.bar.
Clients which expose these config options to the end-user are advised to match the option names and, if possible data structures. Some clients (VS Code extension) may however use flat structure, such as {"foo.bar": "..."} if using objects is not possible or practical.
The language server supports the following configuration options:
Terraform CLI related settings (used e.g. in formatting code via terraform fmt).
Path to a file for Terraform executions to be logged into (TF_LOG_PATH)
with support for variables (e.g. Timestamp, Pid, Ppid) via Go template
syntax {{.VarName}}
Overrides Terraform execution timeout in time.ParseDuration
compatible format (e.g. 30s)
Path to the Terraform binary.
This is usually looked up automatically from $PATH and should not need to be
specified in majority of cases. Use this to override the automatic lookup.
Deprecated in favour of terraform.logFilePath
Deprecated in favour of terraform.timeout
Deprecated in favour of terraform.path
This option is deprecated and ignored from v0.29+, it was used as an escape hatch
to force indexing of paths in cases where indexer wouldn't index them otherwise.
Indexer in 0.29.0 no longer limited to just initialized modules (folders with .terraform)
and instead indexes all directories with *.tf files in them.
Therefore this option is no longer relevant.
If you previously used it to force indexing of a folder outside of a workspace, you can just add that folder to the workspace and it will be indexed as usual.
Deprecated in favour of indexing.ignorePaths
Paths to ignore when indexing the workspace on initialization. This can serve
as an escape hatch in large workspaces. Key side effect of ignoring a path
is that go-to-definition, go-to-references and generally most IntelliSense
related to local module blocks will not work until the target module code
is explicitly opened.
Relative paths are resolved relative to the root (workspace) path opened in the editor.
Path separators are converted automatically to the match separators
of the target platform (e.g. \ on Windows, or / on Unix),
symlinks are followed, trailing slashes automatically removed,
and ~ is replaced with your home directory.
This allows excluding directories from being indexed upon initialization by passing a list of directory names.
The following list of directories will always be ignored:
.git.idea.vscodeterraform.tfstate.d.terragrunt-cache
Deprecated in favour of indexing.ignoreDirectoryNames
Some clients such as VS Code keep a global registry of commands published by language servers, and the names must be unique, even between terraform-ls instances. Setting this allows multiple servers to run side by side, albeit the client is now responsible for routing commands to the correct server. Users should not need to worry about this, the frontend client extension should manage it.
The prefix will be applied to the front of the command name, which already contains
a terraform-ls prefix.
commandPrefix.terraform-ls.commandName
Or if left empty
terraform-ls.commandName
This setting should be deprecated once the language server supports multiple workspaces, as this arises in VS code because a server instance is started per VS Code workspace.
This setting controls whether terraform-ls sends a warning about opening up a single Terraform file instead of a Terraform folder. Setting this to true will prevent the message being sent. The default value is false.
This object contains inner settings used to opt into experimental features not yet ready to be on by default.
Enabling this feature will run terraform validate within the folder of the file saved. This comes with some user experience caveats.
- Validation is not run on file open, only once it's saved.
- When editing a module file, validation is not run due to not knowing which "rootmodule" to run validation from (there could be multiple). This creates an awkward workflow where when saving a file in a rootmodule, a diagnostic is raised in a module file. Editing the module file will not clear the diagnostic for the reason mentioned above, it will only clear once a file is saved back in the original "rootmodule". We will continue to attempt improve this user experience.
Enables advanced completion for provider, resource, and data blocks where any required fields for that block are pre-filled. All such attributes and blocks are sorted alphabetically to ensure consistent ordering.
When disabled (unset or set to false), completion only provides the label name.
For example, when completing the aws_appmesh_route resource the mesh_name, name, virtual_router_name attributes and the spec block will fill and prompt you for appropriate values.
This object contains settings related to validation unless it's experimental,
in which case it's under experimentalFeatures.
Enables/disables enhanced validation, as documented under validation.md.
The server expects static settings to be passed as part of LSP initialize call,
but how settings are requested from on the UI side depends on the client.
Use initializationOptions key under the clients.terraform section, e.g.
{
"clients": {
"terraform": {
"initializationOptions": {
"rootModulePaths": ["/any/path"]
},
}
}
}or
{
"clients": {
"terraform": {
"initializationOptions": {
"excludeModulePaths": ["/any/path"]
},
}
}
}Use terraform-ls, e.g.
{
"terraform-ls": {
"rootModulePaths": ["/any/path"]
}
}or
{
"terraform-ls": {
"excludeRootModules": ["/any/path"]
}
}