> This is intensely frustrating when the setting is tied to a CI pipeline that takes 5 minutes to get to the error. I also detest this, but it's not really abo

> This is intensely frustrating when the setting is tied to a CI pipeline that takes 5 minutes to get to the error. I also detest this, but it's not really about YAML - it's ridiculous that so many of our tools no longer allow any validation / linting of files before attempting to use them; some that do require the "full service" running to provide sufficient context; even those that don't don't always give good (i.e. consistent, structured) errors. This problem would remain if the format was JSON, TOML, or even XML when working without schemas for every namespace. The worst is the tools that layer Jinja on top of the YAML (Salt/Ansible/Puppet) which is basically impossible to validate statically. At least with GitLab, Docker Compose, and Kubernetes I have some hope - but integration into other tools is awful.