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
- After the creation steps, a verification step checks that all expected alert issues and rule parents exist.
- Workflow fails or emits a clear warning if any are missing.
- 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
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
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