Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Schema validation error does not help identify the source of error #833

Open
singhprincejeet opened this issue Nov 8, 2022 · 0 comments
Labels
enhancement New feature or request up for grabs Looking for a contributor to take this task

Comments

@singhprincejeet
Copy link

Is your feature request related to a problem? Please describe.
When I see a schema validation error, it does not help me identify where the issue is.

For ex, in this error: k8s schema validation error: For field spec.tls.1: Additional property host is not allowed

It does not give any specific info on where the error would be. Kubeconform shares the kind of the resource which has error. If we could see that then it would be easy to find where the error is.

Describe the solution you'd like
Error messages to include the kind of the resource which has error. This would help identifying the source of the issue.

Describe alternatives you've considered
Using kubeconform to test schema validation and use datree only for policy rules.

@singhprincejeet singhprincejeet added the enhancement New feature or request label Nov 8, 2022
@eyarz eyarz added the up for grabs Looking for a contributor to take this task label Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request up for grabs Looking for a contributor to take this task
Projects
None yet
Development

No branches or pull requests

2 participants