Fence generated artifact retention

This commit is contained in:
2026-08-03 03:54:58 +02:00
parent 9da03090a7
commit 50ce8b0acb
5 changed files with 435 additions and 12 deletions
+5 -2
View File
@@ -156,8 +156,11 @@ before attempting delivery.
business fields.
- A build failure deletes objects written before the database transaction can
commit.
- Retention clears metadata only after object deletion succeeds; an unavailable
backend leaves the reference in place for a later retry.
- Retention starts a job-fenced forward-recovery operation before deletion,
commits metadata changes in the Campaign-owned boundary, and independently
probes the original locator before reporting success. An unavailable backend
leaves an outcome-unknown operation; a deletion/metadata mismatch becomes
recovery-required in Ops.
- A hard process loss between object creation and metadata commit can leave an
orphan object. Reconcile only within the Campaign build prefix and verify that
no job references the object before deleting it.