alligotor
isopod
alligotor | isopod | |
---|---|---|
2 | 4 | |
22 | 462 | |
- | 0.4% | |
1.5 | 0.0 | |
4 days ago | 6 months ago | |
Go | Go | |
MIT License | 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.
alligotor
-
A lightweight package for loading environment variables into structs
It's probably not a new idea but I still have to say I really like the package design and also how you designed the readme. I wrote a similar package a while back with the same thing in mind and it still works great for me. Maybe that's why I like yours 😅
-
Alligotor v0.2.0 - configuration package
If you're interested you can find usage examples at https://github.com/brumhard/alligotor or https://pkg.go.dev/github.com/brumhard/[email protected].
isopod
-
Jsonnet – The Data Templating Language
Tried it[0], worked reasonably well. Be prepared for strong opposition from traditional “devops” folks “who don’t mind yaml” and will drag everyone down.
[0] - https://github.com/cruise-automation/isopod
- Deploying Kubernetes clusters in increasingly absurd languages
- YAML: It's Time to Move On
-
Cue: A new language for data validation
I like Cue and Jsonnet and Starlark and so on. But all of these have very low mindshare (though Starlark has the most momentum thanks to Bazel), and who knows if they will be dead by next year.
Being an early adopter is difficult both in terms of the immaturity of the tooling — Cue, for example, only has a Go implementation at the moment — and in terms of the risk of betting on an evolutionary dead end, which can cause a lot of unnecessary churn when you want to standardize on something across an entire organization.
As a concrete example, I'd love to replace Kubernetes's use of YAML with something like the above. But the tooling is immature, and almost nobody is using any of it. For example, there's Isopod [1], which is a nice-looking tool to use Starlark with Kubernetes. But it might go the same way as Ksonnet.
[1] https://github.com/cruise-automation/isopod
What are some alternatives?
env - 🔍 Load environment variables into a config struct
skycfg - Skycfg is an extension library for the Starlark language that adds support for constructing Protocol Buffer messages.
env - A simple and zero-dependencies library to parse environment variables into structs
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
dasel - Select, put and delete data from JSON, TOML, YAML, XML and CSV files with a single tool. Supports conversion between formats and can be used as a Go package.
rules_jsonnet - Jsonnet rules for Bazel
go-toml - Go library for the TOML file format
kubecfg - A tool for managing complex enterprise Kubernetes environments as code.
koanf - Simple, extremely lightweight, extensible, configuration management library for Go. Support for JSON, TOML, YAML, env, command line, file, S3 etc. Alternative to viper.
c2bf - Compiler from C to brainfuck
jk - Configuration as Code with ECMAScript
typescript-json-schema - Generate json-schema from your Typescript sources