AbsaOSS / AbsaOSS/organizational-workflows
Add control checksum to workflow code for alert/rule integrity
- Vorherrschende Sprache
- Python
- Sterne
- 0
- Forks
- 0
- Ø Merge
- 5 T. 3 Std.
- Gemergte PRs (30 T.)
- 3
Beschreibung
### 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_
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.