4 ms·
Marcin here, one of the OpenTF folks This repo [0] seems to still be licensed under MPL, so there is no need for an immediate action, but if there is a willing
by fishnchips 3y ago
Marcin here, one of the OpenTF folks
This repo [0] seems to still be licensed under MPL, so there is no need for an immediate action, but if there is a willingness in the community to take it over and improve, I see no reason why we wouldn't do it.
[0] https://github.com/hashicorp/terraform-ls https://github.com/hashicorp/terraform-ls
- bloopernova 3y agoI can't imagine how much you all have on your plates right now, so this can definitely wait. Tools, frameworks, etc all have to be written by people, and I'm sure you're already keenly aware that poor programmer tooling can be the death of a project. This is definitely selfish on my part since I write a lot of Terraform and lean on the language server a lot, but I hope that terraform-ls can have a couple of people dedicated to it eventually. Unfortunately (of course!!) my own pet issues are pretty niche, since I expect there aren't many people using a lot of private registry modules like the client I work for. Hence my desire to fix it myself :)
- mdaniel 3y ago> but I hope that terraform-ls can have a couple of people dedicated to it eventually. I 100% agree with your perspective on tooling, and hope the OpenTF team will take terraform-ls (and hcl-lang) under their org, too, because I will never contribute one more character to any repo in the hashicorp org. Adopting hcl-lang is very low risk, but not zero, and it would be a spiteful move for Hashicorp to introduce some BuSL-only change to hcl for the purpose of hard-forking the language