feat(cli): expose structured violation data in policy develop eval output#2969
Merged
migmartri merged 1 commit intochainloop-dev:mainfrom Mar 31, 2026
Conversation
b135567 to
7046780
Compare
…tput Automatically populate structured_violations in the eval output when the policy returns structured finding data. Uses protojson to serialize the proto violations directly — no custom types needed. The violations field (string messages) remains populated for backward compatibility. Closes chainloop-dev#2968 Signed-off-by: Miguel Martinez <migmartri@gmail.com> Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
7046780 to
1135617
Compare
matiasinsaurralde
approved these changes
Mar 30, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
structured_violationsinpolicy develop evaloutput when the policy declares afinding_typeand violations contain structured finding dataprotojsonto serialize proto violations directly, no custom types neededviolationsfield (string messages) remains always populated for backward compatibilityCloses #2968