gapline reads its configuration from TOML files. Unknown keys are rejected: a typo in a section or field produces a parse error with the path to the offending file. See getting started / configuration for how the lookup chain works.
This page documents every accepted key. Some are forward-compatible stubs — they deserialize cleanly but are not yet read by any runtime code. They are documented for completeness and will become live as the features land. gapline logs a warning when one of them is set to a non-default value.
Filter out findings below this level. Overridden by --min-severity.
disabled_rules
array of string
[]
Rule IDs or finding codes to skip (see validation rules). Each foreign key has its own fk_<file>_<field> ID; foreign_key_violation selects them all. CLI --disable-rule appends to this list.
max_rows
integer
—
Maximum data rows per file (consumed by TooManyRowsRule). Omit to disable the check.
fail_fast
boolean
false
Stop after the first post-parse section that reports an error.
max_errors_per_rule
integer
—
Forward-compat. Not yet wired.
enabled_rules
array of string
[]
When non-empty, only these rule IDs or finding codes run. disabled_rules wins on conflict.
A missing config file (any of the three lookup layers) is silently skipped.
A file that exists but cannot be read (permission denied, I/O error) aborts with exit code 3.
A file that parses to invalid TOML, or contains an unknown key, aborts with exit code 2 and a message that includes the path and the offending token.
A semantically invalid value (negative speed, zero calendar coverage, incoherent thresholds) aborts with exit code 2 and a message that cites the specific field.