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
While providers can practically only be defined in a single place in config, it may not always be quick and easy to find that place and understand the implications.
Users would benefit from seeing what providers are required and installed for their module at a quick glance.
Expected User Experience
The expectation is that we'd use Tree View API, which would look approximately like this:
we may also consider adding the view directly under the Explorer menu, similar to this example from VS Code docs:
User would be able to see:
provider requirements for the module(s) being edited
provider versions installed for the module(s) being edited
any alternative names which each provider is available
any aliases under which each provider is available
right click to update outdated provider
right click to go to the docs of the provider, where applicable (Terraform Registry)
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.
Use Cases
While providers can practically only be defined in a single place in config, it may not always be quick and easy to find that place and understand the implications.
Users would benefit from seeing what providers are required and installed for their module at a quick glance.
Expected User Experience
The expectation is that we'd use Tree View API, which would look approximately like this:
we may also consider adding the view directly under the Explorer menu, similar to this example from VS Code docs:
User would be able to see:
We may also consider implementing this as a WebView https://code.visualstudio.com/api/extension-guides/webview
Proposal
The text was updated successfully, but these errors were encountered: