Structs§
Functions§
- delete_
marker_ purge_ mrf_ entry - Shape an exhausted purge intent as a marker-creation delete entry. Replay
reconstructs it with
delete_marker: true, finds the source marker gone, and funnels into the stale-marker branch ofreplicate_delete_with_outcome— which re-runs the purge without touching source state and reports purge success as the replay outcome. - delete_
marker_ purge_ version_ id - Which version a delete-marker purge should address on one target.
- delete_
replication_ creates_ marker - Whether the target DELETE for this delete replication may use
marker-CREATION semantics (
replication_delete_marker, which omits theversionIdquery so the target mints its own marker). - delete_
replication_ target_ version_ id - The version a delete replication addresses on
arn, orNoneto refuse. - is_
object_ lock_ denied_ delete - True when the target denied a replicated delete because object-lock
retention or a legal hold protects that version on the replica (its
deletion gate answers
AccessDeniedwith the lock reason, and a replication request carries no governance bypass, rustfs#6850). Retrying cannot succeed until the lock itself lapses, so callers treat this as a policy denial rather than a transient fault. - is_
retryable_ delete_ replication_ head_ error - is_
version_ delete_ replication - replicate_
delete_ outcome - Whether a delete replication fully succeeded — the MRF replay acknowledges (drops) an entry exactly when this returns true.
- resync_
existing_ delete_ replication_ info - Build the delete-replication work item for an existing delete marker or version purge discovered during a resync scan.
- should_
retry_ delete_ marker_ purge - target_
delete_ version_ id