AbsaOSS / AbsaOSS/organizational-workflows

Add control checksum to workflow code for alert/rule integrity

Aperta
#21 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
enhancement
Lingua principale
Python
Stelle
0
Fork
0
Merge medio
5g 3h
PR unite (30g)
3

Descrizione

### 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_

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.