3 ms·
I’m one of the maintainers of the project. We’re a DevOps team and maintain a lot of different types of configuration files for all the different tools and serv
by treebeard5440 3y ago
I’m one of the maintainers of the project. We’re a DevOps team and maintain a lot of different types of configuration files for all the different tools and services we support - often in the same repo. Rather than using a lot of different validators for each config format we wanted a single tool to validate all types. This enabled us to include config validation as a quality gate in our CI/CD to detect config file syntax issues early before they failed in functional testing. We open-sourced it to help other teams with similar workflows. Please let me know if you have any comments or suggestions!
- AndyKluger 3y agoI feel like I missed it, but what kind of validation rules are used?
- treebeard5440 3y agoRight now we’re just checking if the file is valid json, xml, toml, etc. Someone mentioned validation rules in another comment which is a great suggestion and something we’ll work to implement. It would also be nice to validate the configs for different tools like GitLab yaml, kubernetes config, etc. We’re still thinking through how to best implement something like that in an extensible/pluggable way.
- zvr 3y agoI think you should make clear that you are talking about syntactic validation and not any kind of semantic one.
- treebeard5440 3y agoTotally agree, for the initial release it was not ever on our radar to do semantic validation (although I really like the idea of adding that down the road). I’ll make sure to update the README to make sure that’s clear