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

Use registry schema cache if no initialized data for providers #193

Open
paultyng opened this issue Jun 30, 2020 · 1 comment
Open

Use registry schema cache if no initialized data for providers #193

paultyng opened this issue Jun 30, 2020 · 1 comment
Labels
enhancement New feature or request providers Functionality related to Terraform providers upstream/tf-registry

Comments

@paultyng
Copy link
Contributor

Use-cases

  • Brand new workspaces (or newly added providers) have no init data
  • Unable to init workspace for some reason (ie. only init/plan/apply via CI/CD, etc)

Proposal

The Terraform registry can provide an endpoint that serves the schema JSON for a provider. The LS can use this endpoint to pull the information to the local provider schema cache in scenarios where a root module / local init is not present/possible.

@TheFlyingArcher
Copy link

Is this issue on your roadmap? The way my company does our Terraform structure, it is unfeasible to run terraform init on all directories to obtain autocompletion and intellisense. As such, I'm without these key features of the extension.

This sounds like a good feature and would benefit the LS.

@radeksimko radeksimko mentioned this issue Jun 6, 2022
@xiehan xiehan added the providers Functionality related to Terraform providers label Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request providers Functionality related to Terraform providers upstream/tf-registry
Projects
None yet
Development

No branches or pull requests

4 participants