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
Relatedly we can also highlight what TF version is required and available, e.g.
Terraform ~> 0.14 (0.14.9)
Proposal
Expose a custom command, such as moduleinfo which can expose details about the module's metadata that can be leveraged by clients and potentially somehow displayed in the UI.
Such command could just pull all that info out of the state store.
The only question is how do we ensure that the client always has up-to-date data - it would likely need to be requesting the data all the time, similar to how the old rootmodules command is wired in the VS Code extension.
The text was updated successfully, but these errors were encountered:
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.
Current Version
Use-cases
Similar to how symbols provide a high-level overview of the code structure:
We can provide some kind of overview of the providers in use which were parsed for a given module, e.g.
Relatedly we can also highlight what TF version is required and available, e.g.
Proposal
Expose a custom command, such as
moduleinfo
which can expose details about the module's metadata that can be leveraged by clients and potentially somehow displayed in the UI.Such command could just pull all that info out of the state store.
The only question is how do we ensure that the client always has up-to-date data - it would likely need to be requesting the data all the time, similar to how the old
rootmodules
command is wired in the VS Code extension.The text was updated successfully, but these errors were encountered: