-
Notifications
You must be signed in to change notification settings - Fork 0
Expose matched rule description after policy evaluation #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
annacai21
wants to merge
14
commits into
main
Choose a base branch
from
anna.cai/match-description-2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
07ca5d4
Expose matched rule description after policy evaluation
annacai21 d3e9e82
formatting
annacai21 34c7ee0
add a setter function for getitng description with eval details
annacai21 f022d2a
add example hardcoded json file for testing
annacai21 77d4f49
add plcs_eval_ctx_get_matched_description to public header
annacai21 1c06791
formatting
annacai21 bea7303
add stdio.h include
annacai21 d60f56c
change logic to match description of innermost node
annacai21 c2e7b0f
derive human-readable match description from policy tree structure
annacai21 bdcabf1
simplify test cases
annacai21 7aba427
remove action_entry.error
annacai21 579c501
formatting
annacai21 783a7a8
remove test for deleted plcs_eval_ctx_set_action_error
annacai21 602c299
include runtime context value in matched description
annacai21 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you discussed the possibility of generating the description in the backend instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the concern was that generating on the backend would make it harder to include runtime context (which arg matched, what value triggered the rule, etc.), since that information is only available at injection time. It would also require the backend to maintain an enum -> description mapping, meaning policy changes would need to be coordinated across repos. I'd lean toward keeping it in dd-policy-engine for those reasons, but if you have other thoughts let me know!