nestedtextto
tanka
nestedtextto | tanka | |
---|---|---|
5 | 25 | |
16 | 2,236 | |
- | 2.1% | |
9.6 | 8.3 | |
3 days ago | 6 days ago | |
Python | Go | |
Do What The F*ck You Want To Public 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.
nestedtextto
-
The yaml document from hell
I used the official reference implementation to make a CLI converter between NestedText and TOML, JSON, and YAML. When generating one of these formats, you can use yamlpath queries to concisely but explicitly apply supported types to data elements.
-
The YAML Document from Hell
I'm a huge fan of NestedText, especially as there is no escaping needed ever.
If you ever want to use it as a pre-format to generate either TOML, JSON, or YAML, I used the official reference implementation to make a CLI converter between them and NestedText.
When generating one of these formats, you can use yamlpath queries to concisely but explicitly apply supported types to data elements.
- My CLI converter: https://github.com/AndydeCleyre/nestedtextto
- yamlpath info: https://github.com/wwkimball/yamlpath/wiki/Search-Expression...
-
A practical issue with YAML: your schema is not documentation
In case you're interested and haven't seen it, I've become a big fan of NestedText, which is similar to YAML but without the complicated parts, and without types (just strings, lists, and dicts). The idea is that any meaningful validation and coercion belongs in code anyway. An extra cool part is that nothing ever needs to be escaped, so the content is super clean and unambiguous.
If you want to play around with it, I made NestedTextTo (nt2 on PyPI), for CLI conversion between NestedText and YAML, TOML, or JSON, with a pretty cool (IMO) way to cast value types along the way.
https://nestedtext.org/en/stable/ (not my project)
https://github.com/AndydeCleyre/nestedtextto (my project)
-
How do you yaml
I recently fell in love with the NestedText format, and whipped up a CLI for conversions between it and YAML (and JSON and TOML), so now whenever manually viewing those other formats I pipe it through into readable NestedText. In this example, the result is identical to format A.
-
nt2: a CLI converter between NestedText and JSON, YAML, or TOML
So I made nt2 (NestedTextTo) (install from PyPI as nt2[toml] for TOML support).
tanka
-
Why the fuck are we templating YAML? (2019)
I would recommend implementing a similar API to Grafana Tanka: https://tanka.dev
When you "synthesise", the returned value should be an array or an object.
1. If it's an object, check if it has an `apiVersion` and `kind` key. If it does, yield that as a kubernetes object and do not recurse.
-
What Is Wrong with TOML?
Maybe you'd like jsonnet: https://jsonnet.org/
I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev).
Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/
A few years ago I did a small comparison by re-implementing one of my simpler ansible playbooks: https://github.com/retzkek/ansible-dhall-jsonnet
-
Show HN: Keep β GitHub Actions for your monitoring tools
- validation is often impractical (at least identifying exactly where the error isβ¦ Iβm looking at you Helm!)
Unrelated to OP, but you can leverage Tanka to extend helm charts with functionality not provided by upstream.
https://tanka.dev/
-
Alternatives to Helm?
Although jsonette might be considered more complex Tanka is a great alternative for k8s config management.
- Helm makes it overly complex, or is it just me?
-
The YAML Document from Hell
At Grafana Labs we're using jsonnet at scale, while being a powerful functional language it is also excellent for rendering JSON/YAML config. We have developed Tanka[0] to work with Kubernetes, for other purposes I can recommend this course[1] (authored by me).
[0] https://tanka.dev/
[1] https://jsonnet-libs.github.io/jsonnet-training-course/
-
Should i migrate from Kustomize to Helm?
If you're hitting the limits of Kustomize, maybe look at Tanka as well.
-
Is it possible to wrap Kustomize yaml with jinja2?
Yes, try Tanka.
-
Using Docker β Compose in Development and Production
yes. basically. and this is a path that multiple people are trying to solve. e.g. AWS CDK8s, https://tanka.dev/, etc
Compose would be awesome.
-
Google Kubernetes clusters config checker tool
http://tanka.dev
(Note I work for Grafana Labs who fund Tanka and use it for all production config)
What are some alternatives?
sexplib - Automated S-expression conversion
helm-charts - Prometheus community Helm charts
lua-sandbox - A lua sandbox for executing non-trusted code
kustomize - Customization of kubernetes YAML configurations
sexp - S-expression swiss knife
kapitan - Generic templated configuration management for Kubernetes, Terraform and other things
cels - Command line tool to patch your YAML, JSON and TOML files.
ytt - YAML templating tool that works on YAML structure instead of text
strictyaml - Type-safe YAML parser and validator.
kpt - Automate Kubernetes Configuration Editing
sxpyr - Parse s-expressions, edn, and a variety of lisp dialects.
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages π