AbsaOSS / AbsaOSS/organizational-workflows

Add control checksum to workflow code for alert/rule integrity

Ouverte
#21 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
enhancement
Langage dominant
Python
Étoiles
0
Forks
0
Merge moyen
5 j 3 h
PR mergées (30 j)
3

Description

### Feature Description

Introduce a checksum or integrity-check mechanism in workflow code to verify that all planned alert issues and rule parents have been successfully created.

### Problem / Opportunity

Currently there is no automated confirmation that all expected alert issues and rule parent records were created. Silent failures or partial runs can lead to undetected configuration gaps.

### Acceptance Criteria

1. After the creation steps, a verification step checks that all expected alert issues and rule parents exist.
2. Workflow fails or emits a clear warning if any are missing.
3. The expected list is configurable or derived from workflow inputs.

### Proposed Solution

After the creation phase, add a validation step that queries the created entities and compares them against the expected set (checksum/count or explicit list). Fail the workflow with a descriptive message if a mismatch is detected.

### Dependencies / Related

_No response_

### Additional Context

_No response_

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.