Skip to main content

Module object

Module object 

Source

Structs§

ReplicationSourceObject
ReplicationTargetObject

Enums§

ObjectLockIntegrity
How a replication PutObject that carries Object Lock parameters satisfies the target-side rule that such a request must also carry Content-MD5 or an x-amz-checksum-* header (AWS S3, MinIO and most compatible stores enforce it; rustfs#7082).
SsecPassthroughCapability
Whether a replication target preserves the SSE-C passthrough transport headers (X-Rustfs-Replication-*) end to end.
SsecPassthroughGate
Fail-closed decision for an SSE-C passthrough replication attempt, derived from the target’s cached SsecPassthroughCapability. Pure so the policy can migrate with the worker (M2) without dragging the cache along; the caller computes expired from the cache record’s age (see the runtime’s SSEC_PASSTHROUGH_CAPABILITY_TTL).
VersionIdentityCapability
Whether a replication target adopts the source version id it is handed on PutObject / CompleteMultipartUpload, or mints its own.

Functions§

content_matches_by_etag
is_replication_target_offline_error
True when a target operation error reads as a network/transport failure — the only class of error that should mark a replication target offline.
object_lock_put_integrity
Decide the integrity header for a locked replication PUT.
replication_action_for_target
replication_etags_match
single_part_replica_etag_mismatch
Whether the ETag the target returned for a single-part replica proves the stored bytes differ from what the source sent — e.g. a target that does not decode aws-chunked framing stores the frames verbatim and returns their ETag. Only a plain single-part MD5 ETag on both sides is decidable; a multipart or opaque (encrypted) ETag, or a withheld replica ETag, returns false because no corruption can be concluded from it.
ssec_passthrough_evidence_present
True when a replication-check HEAD of the replica proves the SSE-C material survived passthrough: a RustFS target restores the transport headers into the stored SSE-C keys and its HEAD echoes x-amz-server-side-encryption-customer-algorithm (the replication-check exemption skips key validation but not the metadata echo). A target that dropped the headers stored a plain object and echoes nothing. The caller extracts the echoed customer-algorithm value from its HEAD response type.
ssec_passthrough_gate
target_is_newer_than_source_null_version
version_identity_capability_from_put
Judge the identity contract from one replication write: None when no contract applies (the source addressed no real version — an empty or nil uuid travels as the literal “null”, unversioned-source semantics), otherwise whether the target echoed the source id or answered with anything else — including nothing at all.
version_identity_drifted
Runtime half of the P1-19 version-identity contract (the explicit probe lives in replication-check’s VersionFidelity phase): every replication PUT response reveals whether the target adopted the source version id. A target minting its own ids silently breaks version-addressed deletes and heal, so surface it — once per target — instead of letting the divergence accumulate unseen. Pure drift judgment: the contract only applies when the source addressed a real (non-nil) version uuid, and drift means the target answered with anything else — including nothing at all.