Error Reports can be much more specific

[FarzanRNobakht]

I have a yaml file containing configurations for multiple Kubernetes resources

when i run kubeval

I get a one line report!:

* Missing a kind key

and it does not specify where in file the error has occured

[garethr]

Good idea. I'll look into whether the YAML parser exposes this information, or I need to do something when handling errors of that type.

[wkhere]

Yep,

adding a line number would be an obvious helpful addition to the error reporting

[orrc]

Similarly, indicating which file failed would be useful. e.g. this runs against 16 files, but aborts if a single file fails, without mentioning which one:

$ kubeval -v 1.11.4 --strict **/*.yml
1 error occurred:

* Missing a kind key

And yes, line number would definitely be useful, e.g. a situation I just had: 😄

$ kubeval -v 1.11.4 --strict **/*.yml
…
The document dev/foo_deployment.yml contains an invalid Deployment
---> name: Additional property name is not allowed

$ grep name: dev/foo_deployment.yml | wc -l
      23

[sgalsaleh]

Any updates on this?

[ghost]

Any updates?

[uberspot]

+1 for a --verbose flag.

[tielur]

+1 this would be super helpful RIGHT now 😆