Re:Validating Kubernetes YAML for best practice and policies
by tyfon on Sunday August 09, 2020 @11:51AM
(#24100369)
Also, YAML is kind of a hack.
Living in Norway I've had quite a few of these situations where no is parsed to False [1].
[1] https://hitchdev.com/strictyaml/why/implicit-typing-removed/
Re:Validating Kubernetes YAML for best practice and policies
by ithkuil on Sunday August 09, 2020 @01:58PM
(#24101477)
It has been fixed since yaml 1.2
That said, yeah :facepalm:
Re:Validating Kubernetes YAML for best practice and policies
by ithkuil on Sunday August 09, 2020 @01:57PM
(#24101464)
> powerful as yaml
Can you make an example of the power of yaml that makes it more like a programming language (in particular vs JSON)?
Re:Validating Kubernetes YAML for best practice and policies
by riffraff on Sunday August 09, 2020 @02:04PM
(#24101537)
not OP but: tags (custom data types), more builtin data types (dates etc), more syntax variations (heredocuments, multiple ways to write a string,a boolean, etc), comments, references+aliases.
The language is vast, and most people use it without knowing it.
I love YAML, but I wish there was a "strict&sane yaml subset".
Re:Validating Kubernetes YAML for best practice and policies
by ithkuil on Sunday August 09, 2020 @03:37PM
(#24102230)
All those are good examples of yaml complexity but none of that is anywhere near what even a simple programming language can unleash (variables, loops, functions, recursion etc)
Re:Validating Kubernetes YAML for best practice and policies
by Znafon on Sunday August 09, 2020 @06:53PM
(#24103641)
You can do recursion in YAML, and it ends badly: https://en.wikipedia.org/wiki/Billion_laughs_attack#Variatio...
Once you switch to something as powerful as YAML, you might as well reach for a real programming language.