Skip to content
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

Parse comparison expressions when loading policies #300

Merged
merged 2 commits into from
May 18, 2021

Conversation

bluekeyes
Copy link
Member

Expressions are functionally equivalent to before, but are now validated
as part of the validation endpoint. One behavior change is that we now
allow any number of spaces between the operator and the number.

Fixes #289.

Expressions are functionally equivalent to before, but are now validated
as part of the validation endpoint. One behavior change is that we now
allow any number of spaces between the operator and the number.
@bluekeyes bluekeyes requested a review from a team May 14, 2021 20:43
policy/predicate/file.go Show resolved Hide resolved
@bluekeyes bluekeyes merged commit ccf65b1 into develop May 18, 2021
@bluekeyes bluekeyes deleted the bkeyes/comparison-validation branch May 18, 2021 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Policy validation should check for invalid comparison operators
3 participants