- 07
- 08
[ 7, "08" ]
This assumption was discovered deep within some templated YAML generated by templated something else three levels down and resulted in a complete k8s cluster failure for us, but only the 08 cluster! It worked in the first 7.
But fuck this particular type conversion semantic.
Here's a relevant suggestion from the Ansible docs (https://docs.ansible.com/ansible/latest/collections/ansible/...):
For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.
This actually made me LOL, that's amazing
07 is the octal number 7.
08 is not a number.
Did you read the spec? Or did you just start using it assuming you knew how it worked?
Whatever generated that clearly wasn't serializing its data using a library, or it would have converted the type into the correct format.
Wow, you couldn't ask for a stronger condemnation than that for YAML as a configuration language. "You clearly weren't using a library to write your config file".
In the world I live in, config file formats exist to be written and read by humans. Serialization formats exist to be generated by libraries.
But it's not unreasonable to expect 07 and 08 to work consistently.
At least with JSON, tooling can help you find invalid syntax in the middle of your file.
And JSON tooling/libraries (compared to YAML tooling/libraries) are usually faster, easier to use, have less bugs and present less incompatibilities between themselves most of the time.