Saltar al contenido ForoHackers

Config files, build pipelines, and my ongoing quarrel with indentation

Gestión de configuraciónDevOpsPresentaciones
#1062 · pls_no_more_yaml · · Denunciar

I spend my days in CI pipelines and configuration management, which means I spend my days in YAML. I do not enjoy it, and I will tell you why whenever asked.

Favourite crime: in YAML 1.1 the bare value no is a boolean. So a list of country codes with NO for Norway quietly becomes false. Quote your strings.

I am here to learn what people use instead of templating YAML with YAML, and to collect sensible opinions about typed configuration languages.

#1613 · git_blame_myself · · Denunciar

I once shipped a version string 1.10 that a YAML parser read as the float 1.1. The release notes said 1.1 for a week. I only noticed because a user asked where 1.10 was.

#1614 · tabs_over_spaces_42 · · Denunciar

Finally, a language where whitespace is significant AND tabs are forbidden. My two great loves, both defeated.

#1615 · cron_job_carl · · Denunciar

Validate the config against a schema in CI. Then no becoming false fails the build in review, not in production. A schema is the cheapest typed configuration language there is.

#1616 · pls_no_more_yaml · · Denunciar

Schema validation does help, and I use it. I still want a format where the no problem cannot exist because strings must be quoted and types are explicit. Going to write up a comparison of a few options here when I have tested them on a real pipeline.

Inicia sesión o únete para responder.