3 ms·
If this accelerates migration away from Terraform towards a standard, open, IaC platform, then it's a good thing. Something like the JSON version of Terraform t
by bloopernova 3y ago
If this accelerates migration away from Terraform towards a standard, open, IaC platform, then it's a good thing. Something like the JSON version of Terraform that can be generated by different tools, but an open standard instead.
Be "interesting" to see what happens to the recently-renamed Terraform Cloud (now Hashicorp Cloud Platform Terraform :eyeroll:)
Edited to add: I'm guessing the feature I want added to the terraform language server is never going to happen now. Terraform's language server doesn't support registries inside Terraform Cloud, it doesn't know how to read the token in your terraformrc. bleh.
- 0xbadcafebee 3y agoSo basically you want OpenTofu. It's open source, you can make it do whatever you want, and there's a >0% chance your PRs will get accepted (compared to with HashiCorp)
- vundercind 3y ago> Something like the JSON version of Terraform that can be generated by different tools, but an open standard instead. God, please no. The worst thing about all these tools is the terrible formats they keep choosing. Given the directions we’ve (“cutting edge” programmers and server ops folks) chosen to go instead, leaving XML behind was a big mistake. I’d prefer something better, but yaml and json are so terrible that going back to xml would be an improvement.
- dralley 3y agoAgree on YAML, disagree on JSON.
- bloopernova 3y agoYou'd write in a language designed for humans, and that would get translated into a language for computers. In other words, JSON. What are your reasons for disliking JSON?
- vundercind 3y agoTerrible, awful type system. And I just mean at the level of primitive types it can represent, nothing fancy. It doesn’t even have a date type, let alone things like decimals. That’d be my argument specifically against using it to communicate between pieces of software—at least if you’re hand-writing it there’s the excuse that it’s kinda, sorta easy to read and write (at least, people say that—IMO it’s only true for tiny, trivial examples, but that may be a matter of taste) My take on it as a hand-written config/data language is that it’s simply absurd. JSON-schema is terribly unwieldy, but also the lingua franca, so if you want to keep your sanity you write something better to define your data structures (probably in some actual programming language) and generate JSON schema to share structure definitions among readers. Oh my—why?
- mike_hearn 2y agoJSON isn't designed for humans. It's designed, originally, to be eval()d in a browser. HOCON is a JSON-type-system compatible language designed for human config files: https://hocon.dev https://hocon.dev
- bloopernova 2y agoI didn't express myself very clearly, my apologies. I meant that you'd write in a human centric language that would then be translated to JSON. Not editing JSON directly.
- e12e 2y ago> language designed for humans Hardly - it's a hack as a data-only subset of JavaScript, as a sibling comment mentions. It has no support for comments (even though JavaScript does). No support for optimal trailing commas. No integers. No enums.
- bloopernova 2y agoI didn't write very clearly, my apologies. I meant that you'd write in a human centric language that would then be translated to JSON. Not editing JSON directly.
- JojoFatsani 3y agoMaybe you’d like Pulumi?