Download as PDF, PPTX
![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](https://image.slidesharecdn.com/yaml-201203105616/85/YAML-Engineering-why-we-need-a-new-paradigm-13-320.jpg)
Uploaded byRaphaël PINSON
YAML Engineering: why we need a new paradigm
The document discusses YAML engineering and the need for a new configuration paradigm due to complexities in current formats. It highlights YAML's easy readability and machine parsing capabilities while addressing challenges such as security issues and the need for declarative programming. Additionally, it explores various alternatives and advancements in templating languages and configuration management relevant to YAML and JSON.
More Related Content
Similar to YAML Engineering: why we need a new paradigm
YAML Engineering: why we need a new paradigm
- 1. YAML Engineering: Why weneed a new paradigm Raphaël Pinson
- 2. Raphaël Pinson ○ InfrastructureDeveloper / DevOps ○ Augeas & Augeasproviders ○ Voxpupuli @raphink
- 5.
- 7. YAML’s qualities ■ Easyto 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 ofhistory ■ 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 dynamictyping🇳🇴 https://noyaml.com/
- 12. And more numberissues
- 13. Data Types ■ YAMLhas (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 ConfigFormats
- 16. We just needa new format
- 17. YAML as aDSL
- 18.
- 19. Pointers anyone? ■ Factorrepetition ■ Not cross-files ■ Potentially harmful
- 20. Templating vs patching ■Ansible: Jinja2 ■ Helm: Go templates ■ Kompose: patch (merge)
- 21.
- 22.
- 23. Need for Declarative ■Idempotence ■ Convergence / Congruence
- 24.
- 25. YAML is data,not code “Nobody will ever want to program in YAML and Jinja.” Adam Jacob
- 26. In Kubernetes ■ June2014: 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 ofhistory (continued) ■ 1999: XML + XSLT ■ 2001: YAML ■ 2002: JSON (Javascript Object Notation) ■ 2014: Jsonnet ■ 2019: Google CUE + YTT ■ 2020: Dhall
- 28. Generating YAML (orJSON) ■ 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 templatinglangage ■ Simple extension of JSON https://jsonnet.org/
- 30. Kapitan ■ Generic templatedconfiguration 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 configurationlanguage ■ 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 AlphaProvider ■ DSL ■ Alpha ■ Generic manifests
- 36. Pulumi ■ Similar toTerraform in concept/goal ■ Supports multiple languages as DSL: ○ Node.js ○ Python ○ Go ○ .NET Core ○ Go
- 38.