Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display provider requirements/installed in the UI #701

Closed
radeksimko opened this issue Jul 23, 2021 · 1 comment · Fixed by #850
Closed

Display provider requirements/installed in the UI #701

radeksimko opened this issue Jul 23, 2021 · 1 comment · Fixed by #850
Assignees
Labels
enhancement New feature or request

Comments

@radeksimko
Copy link
Member

radeksimko commented Jul 23, 2021

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:

Screenshot 2021-07-23 at 07 45 19

we may also consider adding the view directly under the Explorer menu, similar to this example from VS Code docs:

views

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)

We may also consider implementing this as a WebView https://code.visualstudio.com/api/extension-guides/webview

Proposal

  • decide UI details - i.e. what exact metadata and how we display
  • expose the relevant module data from LS via custom command
  • implement the client-side while leveraging the data from LS obtained via custom command
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants