3 ms·
Because it doesn't make it to your VC in the first place if it doesn't pass schema validation.
by boredtofears 3y ago
Because it doesn't make it to your VC in the first place if it doesn't pass schema validation.
- emodendroket 3y agoExcept you were just talking about "merge conflicts..." two valid versions of the configuration don't necessarily stay valid when they get merged together.
- pjmlp 3y agoBecause a savy developer will validate their schema when sorting out merge conflicts across the whole configuration, instead of commiting a badly merged file that will fail starting up the Kubernetes cluster in the sea of YAML files.