skycfg
sprig
skycfg | sprig | |
---|---|---|
6 | 11 | |
634 | 3,989 | |
0.5% | 0.7% | |
3.9 | 0.0 | |
about 1 month ago | 3 months ago | |
Go | 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.
skycfg
-
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
-
The Dhall Configuration Language
Can you say more about what GCL does better than all of the open source ones?
Anecdotally, I've heard a lot of GCL horror stories, and many Xooglers have chosen to create things like Jsonnet or Skycfg (https://github.com/stripe/skycfg) instead.
- YAML: It's Time to Move On
- Opinion-driven design
-
Migrating Millions of Concurrent WebSockets to Envoy
If you’re looking at other solutions check out https://github.com/stripe/skycfg It works with Envoy and lots of other things that support protobuf configs
-
Yaml Is The Worst Thing Ever Created K8s Should
This is good and there are several other options like https://github.com/stripe/skycfg#why-use-skycfg to add full language support (using Go or python for ex) to configurations.
sprig
-
Templ: A language for writing HTML user interfaces in Go
Standard Go templating seems really lacking if you come from something like Jinja. Even with libraries like https://masterminds.github.io/sprig/ (used e.g. for Helm templating) it feels hard to use.
-
Improve performance of Go serving a React frontend
Eleven, you'd be surprised what go template libs are out there like sprig. https://masterminds.github.io/sprig/
-
What would you choose if you are in my shoes?
If you use Go templates be sure to use Sprig as well to get more usable functions.
-
Library to convert HTML to pdf in Golang
I'd highly recommend tossing in the sprig library and depending on how you break up your templates, maybe creating a custom "include" helper instead of using the built in define/template helpers. The advantage of this is that if each template is capable of rendering itself independently, you can potentially render all of your templates in parallel.
-
Jsonnet – The Data Templating Language
The discoverability of golang templates is terrible, IMHO, since it's missing a "dir(locals())" equivalent and every execution environment gets to make its own rules about what pipelines/functions are exposed
Look at helm as an example: https://helm.sh/docs/chart_template_guide/function_list/ is some of them, https://helm.sh/docs/chart_template_guide/accessing_files/#p... are some others, but they also glued in some version of https://masterminds.github.io/sprig/ So, short of (a) knowing that's the case (b) having 3+ bookmarks in your favorite browser to refer to those reference pages, how would anyone know what pipelines are available?
Separately, I dooooo nooooooot understand why every joker has to invent their own new thing when we have like 50 or so templating languages already. Golang may be an outlier in that competition due to the Google Promotion Packet Effect(tm) but how they came up with `{{ range }}{{ end }}` as sane syntax is some true facepalm, to say nothing of the same landmine that ansible stepped on by not switching jinja2's default characters: `{{` is not _yaml safe_
-
Charm: a new language in, with, and for Go
You mentioned something about PHP. We also already have a templating language in the standard library that can be extended (commonly done with sprig).
-
Is there something similar to plopjs in Go? (generate files based on configuration from templates)
Plopjs looks interesting and is probably not too hard to write for yourself in Go. You could add something like sprig for some useful template functions.
-
Tips for running "good" coding interviews?
Not at all. It was "write a helm template using the following imaginary values in a values file". In 30 minutes, I was able to google the Kubernetes api and the sprig functions for templating, complete the assignment, fix a stupid typo the unit test caught, and spend 5 minutes trying to think of any corner cases that hidden unit tests might catch (I don't know if there were any hidden unit tests). The goal of this take-home assessment was to prove that you are not wasting an engineer's time when they call you, not to prove that you should be hired.
-
tfcmt - Improve Terraform Workflow with PR Comment and Label
Support sprig in Template
-
Kyoto – Build Front End with Golang
They may refer to the definitive shortage of built-in functions. The template engine itself only provides the bare minimum. That's usually not a problem because of template function libraries like https://github.com/Masterminds/sprig
What are some alternatives?
jsonnet - Jsonnet - The data templating language
pongo2 - Django-syntax like template-engine for Go
isopod - An expressive DSL and framework for Kubernetes configuration without YAML
Jet Template Engine for GO - Jet template engine
nestedtext - Human readable and writable data interchange format
liquid - A Liquid template engine in Go
ron - Rusty Object Notation
Plush - The powerful template system that Go needs
rules_jsonnet - Jsonnet rules for Bazel
fasttemplate - Simple and fast template engine for Go
starlark - Starlark Language
amber - Amber is an elegant templating engine for Go Programming Language, inspired from HAML and Jade