You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Cedar, when evaluating policy expressions containing and, or, or if-else statements, the evaluation process stops after partially evaluating the left side of the expression. This partial evaluation can lead to missed opportunities to fully resolve the expression or resolve unknowns on the right side.
Proposed Enhancement
I propose adding a boolean flag to enable full evaluation of policy expressions. This enhancement would allow users to choose between the current partial evaluation behavior and a new full evaluation option.
Benefits
More comprehensive results: Evaluating both sides of an expression can provide a complete picture of the policy's outcome.
Improved resolution of unknowns: Full evaluation help resolve unknowns on the right side of expressions.
Flexibility: Users can choose between partial and full evaluation based on their specific needs.
Category
User level API features/changes
Describe the feature you'd like to request
Current Behavior
In Cedar, when evaluating policy expressions containing
and
,or
, orif-else
statements, the evaluation process stops after partially evaluating the left side of the expression. This partial evaluation can lead to missed opportunities to fully resolve the expression or resolve unknowns on the right side.Proposed Enhancement
I propose adding a boolean flag to enable full evaluation of policy expressions. This enhancement would allow users to choose between the current partial evaluation behavior and a new full evaluation option.
Benefits
Implementation Details
Current Code (Example for
And
expression):Proposed pseudo code:
Current Code for eval_if:
Proposed pseudo code for eval_if:
Describe alternatives you've considered
There is no direct alternative to this approach that achieves the same goals.
Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: