treebeard5440

8 ms·

31.
by treebeard5440 3y ago
Very nice! What are some things you’ve used it for in your home automation?
32.
by treebeard5440 3y ago
This is a cool idea. Can it run outside of the extension ecosystem - like as a cli tool? I could see some use-cases/integration using it that way but not as much as an extension
33.
by treebeard5440 3y ago
Is this not available via the aws cli/api?
34.
by treebeard5440 3y ago
Well now I know what I’m doing next weekend - nice work!
35.
by treebeard5440 3y ago
Nice work ya’ll -
36.
by treebeard5440 3y ago
Great suggestions - thanks!
37.
by treebeard5440 3y ago
Anyone else have any suggestions for improvements or things that you'd expect to see in a tool like this? I'll take anything you've got :D All feedback so far has been added as Github issues.
38.
by treebeard5440 3y ago
Neat concept! *'ed
39.
by treebeard5440 3y ago
I really like this concept but struggle to think of how I'd actually use it (admittedly I'm not that creative though). Do you have any suggested use-cases?
40.
by treebeard5440 3y ago
Totally 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
41.
by treebeard5440 3y ago
This is really cool - great work!
42.
by treebeard5440 3y ago
I like how you broke this down - it’s really not that hard
43.
by treebeard5440 3y ago
Right 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
44.
by treebeard5440 3y ago
Cool library and great suggestion. We hadn’t needed that level of validation (originally created to be a guard against syntax errors from manual edits) but I really like validation against use cases. Appreciate the feedback - this is exactl
45.
by treebeard5440 3y ago
Very cool! Thanks for sharing
46.
by treebeard5440 3y ago
Cool project!
47.
by treebeard5440 3y ago
Nice! I’ve been meaning to start learning rust
48.
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 v
49.
Show HN: Config-file-validator – CLI tool to validate all your config files(github.com)
33 points by treebeard5440 3y ago|17 comments
50.
by treebeard5440 3y ago
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 furt