Lifecycle policies in effect on an object must be considered during SCSP operations. In particular, expiration policies must be evaluated to make sure an object is still “live” at the time of the operation before proceeding with the SCSP operation.
SCSP operations on objects in a versioning-enabled bucket must cause any expiration rules in effect to “fire” so that appropriate delete markers are created effectively before the intended behavior of the operation. (PRD 2.2)
The Health Processor must evaluate the lifecycle policy rules in effect and perform the necessary actions implied by those rules. This necessarily means that such rules will be evaluated asynchronously. (PRD 1.5, 1.8, 2.4)
Listing queries are not required evaluate the rules for the objects returned in the listing, thus giving potentially inconsistent results when compared to active SCSP operations.
Listing queries must provide eventual consistency subject to eventual HP evaluation.
General
Content
Integrations