As an infra team we had this same problem. We also had a lot of different configuration types that were required for each tool, often several types being mixed

As an infra team we had this same problem. We also had a lot of different configuration types that were required for each tool, often several types being mixed within the same repo. After a couple of issues with syntax errors making it further down the release than we would have liked we ended up building a single tool to validate all of our configs rather than using a bunch of separate tools. We added it as a quality gate in our pipelines which really helped. We open-sourced it for anyone else going through the same issue: https://github.com/Boeing/config-file-validator https://github.com/Boeing/config-file-validator. It's written in go and runs on Windows, MacOS, and Linux.