Commit 486a784
committed
fix(engine): treat severity_threshold 'none' as no threshold
When severity_threshold is set to "none" (the default in composite
actions), it was being parsed as Severity.UNKNOWN (order 0), causing
every finding to exceed the threshold and returning exit code 1.
Fix _parse_severity() to return None for "none" and handle the same
case in the CLI --severity-threshold override. This fixes the CI
failures in scanner-bandit and scanner-opengrep thin wrappers.1 parent 23912c3 commit 486a784
2 files changed
Lines changed: 14 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
540 | 540 | | |
541 | 541 | | |
542 | 542 | | |
543 | | - | |
544 | | - | |
545 | | - | |
| 543 | + | |
| 544 | + | |
| 545 | + | |
| 546 | + | |
| 547 | + | |
| 548 | + | |
546 | 549 | | |
547 | 550 | | |
548 | 551 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
124 | 124 | | |
125 | 125 | | |
126 | 126 | | |
127 | | - | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
128 | 133 | | |
129 | 134 | | |
| 135 | + | |
| 136 | + | |
130 | 137 | | |
131 | 138 | | |
132 | 139 | | |
| |||
0 commit comments