feat: Add SARIF output support #343
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
Hi @yannh, would you be so kind to review this? Happy to make any changes as needed. 🙏 |
Owner
|
Hi @mridang , I will review this soon! thank you! |
Author
|
My bad. Enjoy the vacays man - code can always wait. 🌴🏝️🏝️🌴 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new output format,
sarif, which generates reports compliant with the Static Analysis Results Interchange Format (SARIF 2.1.0).This allows
kubeconformto integrate directly with tools like GitHub Code Scanning, VS Code extensions, and other CI/CD platforms that support SARIF.-output sarifflag.kubeconformvalidation statuses (Valid,Invalid,Error,Skipped) to the correct SARIF rules and severity levels.ValidationErrorsto create distinct results for each issue, populating thelogicalLocationwith the JSON path of the error (e.g.,spec.replicas).Will add support for #99