Skip to content
This repository was archived by the owner on Jun 6, 2024. It is now read-only.
This repository was 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

Description

@singhprincejeet

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestup for grabsLooking for a contributor to take this task

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions