dhall-kubernetes
terraform-lsp

dhall-kubernetes | terraform-lsp | |
---|---|---|
11 | 5 | |
626 | 579 | |
0.0% | - | |
2.8 | 0.0 | |
5 months ago | almost 2 years ago | |
Dhall | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dhall-kubernetes
-
I Didn't Need Kubernetes, and You Probably Don't Either
One thing that might help you in this madness is:
https://github.com/dhall-lang/dhall-kubernetes
Type safe, fat finger safe representation of your YAMLs is grossly underrated.
-
A skeptic's first contact with Kubernetes
At the moment nothing like that exists. Eventually it should be possible to generate RCL types like https://github.com/dhall-lang/dhall-kubernetes does for Dhall.
-
DSLs Are a Waste of Time
I hate yaml with a passion. It marginally better than xml for reading (wins huge on comment syntax) and worse for everything else. It makes zero sense we somehow ended up with it as standard configuration serialization format.
Note yaml is not a DSL. It's a tree serialization format! Everything interesting is happening after it is parsed. Extreme examples point to e.g. github actions conditions.
Anyway, back on topic - maybe not prolog for CDK, but still quite interesting: Dhall-kubernetes - https://github.com/dhall-lang/dhall-kubernetes
-
Why is Kubernetes adoption so hard?
At this point, if it’s painful enough, why isn’t compiling-to-yml tools more popular?
Example: https://github.com/dhall-lang/dhall-kubernetes
Haven’t used dhall myself but I’d definitely prefer a DSL on top of yaml.
-
Nyarna: A structured data authoring language in the spirit of LaTeX, implemented in Zig
Dhall provides https://github.com/dhall-lang/dhall-kubernetes which is exactly this: statically type-checked kubernetes config generation.
-
The Dhall Configuration Language
Dhall is my favorite configuration language that I never get around to using.
I manage DNS in Terraform, and since every Terraform provider uses different objects definitions, and every object definition is rather verbose, Dhall would be a way to specify my own DRY types and leave the provider-specific details in one place. Adding new DNS entries and moving several domains between providers would be a matter of changing fewer lines.
Dhall also has Kubernetes bindings:
https://github.com/dhall-lang/dhall-kubernetes
Although I'm tempted to just stick to Helm here, even though it's less type-safe.
-
Why helm doesn't use a general purpose programming language for defining resources?
Not Helm directly, but does something like Dhall fit your question? https://github.com/dhall-lang/dhall-kubernetes
-
Dhall configuration language as another way to write manifests for Kubernetes
Have you heard about Dhall? It’s a programming language used for generating configuration files for a variety of purposes. One of them is to replace old and limited formats such as JSON and YAML. It is DRYable, secure, and even suitable for creating K8s manifests. The latter option isn’t something for anyone: you have to learn a new language and deal with its peculiarities, but it might be really helpful when you have tons of YAML configs. I’ve recently made a short intro to Dhall for K8s in this review.
-
Terraform 1.0 Release
Best thing is Dhall that I am aware of. Same situation, working as a consultant, forced to use broken things.
https://github.com/dhall-lang/dhall-kubernetes
-
Write Gitlab CI Pipelines in Python Code
Lets look at a specific example. Take Kubernetes: everything is yaml, with complete schemas, all the way down. From your perspective this is configuration utopia, right? Meanwhile back in reality k8s is the poster child of "yaml hell". From the day it was released, people took one look at it, gave it a giant NOPE and instantly spawned half a dozen templating languages. The most popular of these is helm, which has a terrible, no good, very bad design: full of potential injection attacks from purely textual string substitution, manually specified indentation to embed parameterized blocks, virtually no intermediate validation, no way to validate unused features, etc etc
Compare to dhall which publishes a complete set of dhall-k8s schema mappings which enables you to factor out any design you want down to as few configuration variables as you like, while validating the configuration generators themselves at design time. https://github.com/dhall-lang/dhall-kubernetes#more-modular-...
terraform-lsp
- Help with implementing missing LSP functionality in Terraform
-
Workflow for DevOps? (Ansible, Terraform, Kubernets, RHET)
Look at terraform-ls vs terraform-lsp. Both can be used with coc.nvim.
- Terraform 1.0 Release
-
How to set terraform language pack in spacemacs?
Also installed terraform-lsp as its steps.
-
Using terraform-ls with Kate as LSP Client
Also try terraform-lsp and see if it works.
What are some alternatives?
starlark - Starlark Language
terraform-ls - Terraform Language Server
terragrunt - Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.
tanka - Flexible, reusable and concise configuration for Kubernetes
aws-cloudformation-res
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
terraform-provider-spacelift - Terraform provider to interact with Spacelift
vim-lsp - async language server protocol plugin for vim and neovim
magic-modules - Add Google Cloud Platform support to Terraform
nvim-lspconfig - Quickstart configs for Nvim LSP
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
