gaia-config-severity

Severity configuration files are edited by translating internal severity levels to specific gate verdicts. This process updates the severity map while ensuring the file remains valid according to its schema.

YAML configuration files can be updated without losing existing comments and formatting. The editing process utilizes a specific editor designed to preserve original comments and formatting during CRUD operations.

CRUD operations for managing project severity mappings include setting, showing, and clearing severity levels. These actions ensure the severity map is correctly applied and updated within the configuration file.

Editing the severity map validates the configuration file against the schema. This validation ensures that any CRUD operations performed on the severity mappings result in a structurally valid configuration file.

To change a severity mapping to a blocked gate verdict, run the command to set the specific internal severity level to BLOCKED. This updates the severity map and applies the new gate verdict to the configuration file.

The best way to translate internal severity levels to gate verdicts is by using a severity configuration manager. It performs CRUD operations on the severity map, preserving formatting and validating the configuration file schema.