rules_jsonnet
kubectl-neat-diff
rules_jsonnet | kubectl-neat-diff | |
---|---|---|
1 | 1 | |
64 | 107 | |
- | - | |
6.7 | 10.0 | |
about 1 month ago | over 1 year ago | |
Starlark | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
rules_jsonnet
-
Jsonnet – The Data Templating Language
I can definitely sympathize here - in every context, just straight JSON/YAML configuration seems never expressive enough, but the tooling created in response always seems to come with sharp edges.
Here are some of the things I appreciate about Jsonnet:
- It evals to JSON, so even though the semantics of the language are confusing, it is reasonably easy to eval and iterate on some Jsonnet until it emits what one is expecting - and after that, it's easy to create some validation tests so that regressions don't occur.
- It takes advantage of the fact that JSON is a lowest-common-denominator for many data serialization formats. YAML is technically a superset of JSON, so valid JSON is also valid YAML. Proto3 messages have a canonical JSON representation, so JSON can also adhere to protobuf schemas. This covers most "serialized data structure" use-cases I typically encounter (TOML and HCL are outliers, but many tools that accept those also accept equivalent JSON). This means that with a little bit of build-tool duct-taping, Jsonnet can be used to generate configurations for a wide variety of tooling.
- Jsonnet is itself a superset of JSON - so those more willing to write verbose JSON than learn Jsonnet can still write JSON that someone else can import/use elsewhere. Using Jsonnet does not preclude falling back to JSON.
- The tooling works well - installing the Jsonnet VSCode plugin brings in a code formatter that does an excellent job, and rules_jsonnet[0] provides good bazel integration, if that's your thing.
I'm excited about Jsonnet because now as long as other tool authors decide to consume JSON, I can more easily abstract away their verbosity without writing a purpose-built tool (looking at you, Kubernetes) without resorting to text templating (ahem Helm). Jsonnet might just be my "one JSON-generation language to rule them all"!
---
Though if Starlark is your thing, do checkout out skycfg[1]
[0] - https://github.com/bazelbuild/rules_jsonnet
[1] - https://github.com/stripe/skycfg
kubectl-neat-diff
-
Jsonnet – The Data Templating Language
Original creator of both of those here. I recommend just generating things out straight with the `jsonnet -m` command, and then doing `kubectl diff` on a PR and apply on merge. Scaled huge amount of infra this way and it’s easily understandable and extensible.
To clean up the diff a bit I recommend using: https://github.com/sh0rez/kubectl-neat-diff
Hope it’s helpful!
What are some alternatives?
skycfg - Skycfg is an extension library for the Starlark language that adds support for constructing Protocol Buffer messages.
github-desktop - A version of GitHub Desktop packaged with Conveyor
isopod - An expressive DSL and framework for Kubernetes configuration without YAML
ursonnet - experimental ur-cause tracer for jsonnet
hof - Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.
aperture - Rate limiting, caching, and request prioritization for modern workloads
sprig - Useful template functions for Go templates.
nickel - Better configuration for less
nix - Nix, the purely functional package manager