Match echoed condition keys in CI alert acknowledgements #156
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/ci-health-echo-ack-20261026-e3a447f4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The receiver returns an HTTP202 acknowledgement containing the submitted condition key, so a single static JSON body cannot match acknowledgements for different conditions. Add an explicit exact-echo mode: combine the privately bound static response fields with the generated deduplication key, then require an exact, strict response match. Existing empty and fixed-JSON modes remain unchanged.
Validation: 168 tests pass. Actual loopback HTTP202 and collector tests cover two distinct keys, lost acknowledgements, retries and isolated fault/recovery; malformed, missing, extra, duplicate and mismatched fields fail closed. Independent correction review passed:168 tests,44 repeated calls with unchanged config,34 ACK and19 config countercases, plus all three collector chains. No real receiver call, credential access or monitor activation is performed by this change.