-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add flag to set the maximum error behavior regardless of findings level #1403
Comments
Huh, that's a surprise. I guess we never really used that ourselves. I'll have that fixed. |
Or wait, no. The
So setting it to |
Oh, I misunderstood the flag then. I was looking for a flag for "set the maximum error level to warning" without having to maintain a YAML for all of the rules, manually setting them to Let's change this to a FR then. |
You can set the rules:
default:
level: warning
I'm not opposed to having a flag toggle the default setting outside of conf though. |
That is simple enough, thank you! |
I'd like a flag that lets me set the maximum error behavior, eg treat all errors found as warnings and exit with status code 0. This makes it easier to slowly improve a repo's Rego policies over time without requiring 100% up front effort.
Intended use scenario is to run Regal twice per PR, once in warning-only mode with all checks enabled, once in normal mode with only certain categories enabled. For example:
Over time, more categories would be treated as blocking rather than warnings.
The text was updated successfully, but these errors were encountered: