You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when it comes to understanding relationships between modules (in completion, hover, go-to-definition etc.) we only consider module manifest within .terraform available after modules are installed.
Expecting users to always install modules just to gain the IntelliSense however may be asking for too much.
The following issues represent relevant work that depends on this:
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.
Background
Currently, when it comes to understanding relationships between modules (in completion, hover, go-to-definition etc.) we only consider module manifest within
.terraform
available after modules are installed.Expecting users to always install modules just to gain the IntelliSense however may be asking for too much.
The following issues represent relevant work that depends on this:
module.calls
#725source
andversion
from Terraform Registry #869Proposal
terraform-schema
earlydecoder
to also decodemodule
blocks minimally (in version-agnostic way)ModuleCalls
tomodule.Meta
terraform-ls
state
: AddModuleCalls
tostate.ModuleMetadata
state
: EnsureModuleStore.ModuleCalls()
returns module calls from the configuration in addition to module manifestThe text was updated successfully, but these errors were encountered: