Skip to main content

CAP.L0.INVALID_IGNORE_LIST — the ignore list names something that is not a rule

  • Category: safety
  • Level: 0
  • Stability: stable
  • Suites: audit

An entry in the configured ignore list is not a rule id this package knows.

Why this is refused rather than skipped​

An unrecognized id silently matches nothing. A run with it produces the same output as a run where those findings genuinely stopped occurring — so a project believes a rule is quiet because it was silenced, when in fact it was never silenced and simply has nothing to say yet.

The day it does have something to say, it says it, and the project is surprised by a rule it thought it had turned off months ago.

So the run stops before it connects: a typo in a rule id is a misconfiguration, and the fix is in a file rather than in a database.

What to do​

The notice names the entry it could not resolve. Rule ids are case-sensitive and take the form PG.L2.INDEX_NOT_CONCURRENT — engine, level, name. The shipped registry lists every one of them.

Why an ignore is not a baseline​

An ignore says this never applies here and is meant to stay. A baseline says known, being paid down and is meant to shrink. A project that writes its debt as ignores has a number that never moves — see the audit suite's guidance on which of the two you want.