-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fix bug in response validation rules #287
Fix bug in response validation rules #287
Conversation
Codecov Report
@@ Coverage Diff @@
## main #287 +/- ##
=======================================
Coverage 65.37% 65.37%
=======================================
Files 35 35
Lines 3806 3806
=======================================
Hits 2488 2488
Misses 1133 1133
Partials 185 185
Flags with carried forward coverage won't be shown. Click here to find out more.
|
5f23e9b
to
2aaab99
Compare
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.
This is my bad and I'm sorry about it. We're gonna need to patch the latest release of the Kuadrant Operator with this fix.
Thanks, @adam-cattermole. Nice catch!
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.
🐛 🔫
Let's bring this to https://github.com/Kuadrant/kuadrant-operator/tree/release-v0.4.0 as well. |
There is a bug where if the response field is present, but no response.success field in a submitted
AuthPolicy
it cannot be reconciled by the controller. TheSuccess
field is not a pointer so the validation evaluates to false when trying to add the finalizer.The
exists
check for the routeselectors indynamicMetadata
andheaders
is also inverted.The (second)
AuthPolicy
in the user guide can be used as validation - it fails to reconcile from main but works in this PR: