After updating module to use new version, intellisense for module variables is wrong

[green3g]

Language Server Version

0.36.4

Terraform Version

Terraform v1.11.1 on darwin_arm64

Client Version

vscode HashiCorp Terraform 2.34.3 (2025-01-22)

Terraform Configuration

module "api" {
  source  = "gitlab.com/developer/ecs-service/local"
  version = "4.0.0"
  ...variables

Steps to Reproduce

1. Start with a simple module with an input variable. Publish it as a version to a registry.
2. Reference it in your project and use the existing variables
3. Update the module - modify input variables, add or remove some variables. Publish a new version to a registry.
4. Re-reference the new version in your project and try to use the variables again.
5. The terraform plugin still references the old version's variables and now gives errors when trying to edit the code.

Expected Behavior

The extension should look at the most recent version installed for the module.

Actual Behavior

The extension uses the old - maybe cached version of the module?

Gist

No response

Workarounds

I haven't found one yet - just wondering if this is an issue others are seeing, or if this workflow works for others.

References

No response

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

[Evovita]

Workaround

This worked for me - in the HashiCorp Terraform Extension's settings, toggle ON or OFF the Experimental Features Enable validating the currently open file on save option. You should then be prompted to reload the VS Code window - after pressing the Reload button, the errors should disappear.

In my case this setting was turned OFF on account of Issue 1255, so I turned it back ON. It may be the act of toggling the setting clears a cache of some kind.