Skip to main content

Module delete

Module delete 

Source

Structs§

DeletedObjectReplicationInfo

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 of replicate_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 the versionId query so the target mints its own marker).
delete_replication_target_version_id
The version a delete replication addresses on arn, or None to 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 AccessDenied with 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