YAML Engineering: why we need a new paradigm
•
0 likes•282 views
YAML has become the de-facto standard to express resources in many fields linked to DevOps practices. What are YAML’s strengths and weaknesses, and what are the other options going forward?
Recommended
More Related Content
What's hot
What's hot (20)
Similar to YAML Engineering: why we need a new paradigm
Similar to YAML Engineering: why we need a new paradigm (20)
More from Raphaël PINSON
More from Raphaël PINSON (20)
Recently uploaded
Recently uploaded (20)
YAML Engineering: why we need a new paradigm
- 1. YAML Engineering: Why we need a new paradigm Raphaël Pinson
- 2. Raphaël Pinson ○ Infrastructure Developer / DevOps ○ Augeas & Augeasproviders ○ Voxpupuli @raphink
- 5. YAML
- 7. YAML’s qualities ■ Easy to read by humans ■ Easy to parse by machines ■ Can be used for simple configurations (conf files) ■ Can be used to store data (e.g. Puppet’s Hiera)
- 9. A bit of history ■ 1999: XML + XSLT ■ 2001: YAML ■ 2002: JSON (Javascript Object Notation)
- 10. YAML != XML ■ YAML Ain’t Markup Language ■ Serialization format ■ Maps to Hashes/Arrays
- 11. Say to dynamic typing🇳🇴 https://noyaml.com/
- 12. And more number issues
- 13. Data Types ■ YAML has (loose) data types ■ Some languages (e.g. Ruby) dynamically load types as classes: [10] pry(main)> Puppet.settings.to_yaml.split("n").first => "--- &1 !ruby/object:Puppet::Settings" ■ Security problem
- 15. Too Many Config Formats
- 16. We just need a new format
- 17. YAML as a DSL
- 19. Pointers anyone? ■ Factor repetition ■ Not cross-files ■ Potentially harmful
- 20. Templating vs patching ■ Ansible: Jinja2 ■ Helm: Go templates ■ Kompose: patch (merge)
- 21. Templating YAML
- 23. Need for Declarative ■ Idempotence ■ Convergence / Congruence
- 24. Generators, frontends & DSLs
- 25. YAML is data, not code “Nobody will ever want to program in YAML and Jinja.” Adam Jacob
- 26. In Kubernetes ■ June 2014: YAML added as an alternative to JSON ■ Server starts accepting YAML ■ Expected to be a temporary solution https://www.youtube.com/watch?v=8PpgqEqkQWA
- 27. A bit of history (continued) ■ 1999: XML + XSLT ■ 2001: YAML ■ 2002: JSON (Javascript Object Notation) ■ 2014: Jsonnet ■ 2019: Google CUE + YTT ■ 2020: Dhall
- 28. Generating YAML (or JSON) ■ Most languages can output YAML/JSON ■ But we want declarative code! ■ Avoid imperative coding as much as possible, if possible make it impossible.
- 29. Jsonnet ■ Data templating langage ■ Simple extension of JSON https://jsonnet.org/
- 30. Kapitan ■ Generic templated configuration management for Kubernetes, Terraform & other things ■ Uses Jsonnet, Kadet (alpha) & Jinja2 ■ Components + templates + inventory classes https://kapitan.dev/
- 31. Cue ■ Data-constraint langage ■ Validate, define & use dynamic or text-based data https://cuelang.org/
- 32. YTT ■ VMWare Tanzu ■ Template and patch YAML
- 33. Dhall ■ Programmable configuration language ■ JSON + functions + types + imports ■ Based on Haskell ■ Not Turing-complete guaranteed to return https://dhall-lang.org
- 34. Terraform Kubernetes Provider ■ HCL DSL ■ Stable ■ No generic manifest resource type
- 35. Terraform Kubernetes Alpha Provider ■ DSL ■ Alpha ■ Generic manifests
- 36. Pulumi ■ Similar to Terraform in concept/goal ■ Supports multiple languages as DSL: ○ Node.js ○ Python ○ Go ○ .NET Core ○ Go