We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Device and OS: App version: Kubernetes distro: Kubernetes version: provider:
When you pass empty resources, expected case would be to return a false evaluation but instead is true
false
Basically, this block in validation handles the case correctly:
// Individual result state if lulaValidation.Result.Passing > 0 && lulaValidation.Result.Failing <= 0 { lulaValidation.Result.State = "satisfied" } else { lulaValidation.Result.State = "not-satisfied" }
but in dev validate, only zero failing results are verified, so 0 passing needs to get captured as a "not-satisfied" or false return.
The text was updated successfully, but these errors were encountered:
meganwolf0
Successfully merging a pull request may close this issue.
Environment
Device and OS:
App version:
Kubernetes distro:
Kubernetes version:
provider:
Steps to reproduce
When you pass empty resources, expected case would be to return a
false
evaluation but instead is trueExpected result
Actual Result
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Basically, this block in validation handles the case correctly:
but in dev validate, only zero failing results are verified, so 0 passing needs to get captured as a "not-satisfied" or
false
return.The text was updated successfully, but these errors were encountered: