terraform.codelens.enabled setting doesn't work - "Unknown configuration setting"

Versions

This bug is reproducible in:

• [v2.16.0] the latest version of the extension (below)
• the latest version of the language server (below)

Extension

v2.16.0

Language Server

VS Code

Version: 1.62.3
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T07:59:13.865Z (2 wks ago)
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 19.5.0

Operating System

MacOS Catalina 10.15.5

Terraform Version

Terraform v1.0.11
on darwin_amd64

Steps To Reproduce

Expected Behavior

Actual Behavior

Additional context

[jpogran]

@lkolchin , thanks for the feedback. The ‘authors’ detail and other git information is provided either by the internal Git extension in VS Code or the Gitlens extension (if you have that installed). This is not provided by the Terraform extension and not in our control to decide what is displayed.

The CodeLens functionality placement is decided by VS Code, not our extension. This VS Code issue describes their rationale for not giving an option on placement or display. Unfortunately, that is out of our hands.

The good news is, if you do not want any CodeLens functionality displayed, regardless of which extension is providing it, in any Terraform file right now, you can do so with a language specific editor setting provided by VS Code:

"[terraform]": {
  "editor.codeLens": false
},

This is a useful way to set editor settings per language, so each extension behaves as you desire without affecting other languages. Using this approach, you can add git or other extensions specific codelens settings here to customize what CodeLens functionality is enabled for Terraform files.

Alternately, if you do not want to see any CodeLens for anything ever, you can set the following global setting without a language filter and never see any CodeLens functionality for any extension:

"editor.codeLens": false

Both the git commit and the issue comment you refer to are from before the extension was maintained by HashiCorp and there has been settings changes since then, so searching through issues from 3 years ago won’t be helpful for you. Good news is you don’t have to search through commits or issues to find out what settings an extension has.

To get a listing of current settings, you can open the Extensions Pane and navigate to the HashiCorp Terraform extension, then click on Contribution tab. This shows all commands, settings, and other functionality provided by the extension.

Alternately, you can open the Settings UI where extension specific settings are shown and see all the settings available for this extension.

Lastly, if you open the Settings JSON view inside VS Code it will provide autocomplete intellisense for each setting, once you start typing an extension name.

[github-actions[bot]]

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.