BucketLifecycleRuleExpiration

data class BucketLifecycleRuleExpiration(val createdBeforeDate: String? = null, val date: String? = null, val days: Int? = null, val expiredObjectDeleteMarker: Boolean? = null)

Constructors

Link copied to clipboard
fun BucketLifecycleRuleExpiration(createdBeforeDate: String? = null, date: String? = null, days: Int? = null, expiredObjectDeleteMarker: Boolean? = null)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

Specifies the time before which the rules take effect. The date must conform to the ISO8601 format and always be UTC 00:00. For example: 2002-10-11T00:00:00.000Z indicates that objects updated before 2002-10-11T00:00:00.000Z are deleted or converted to another storage class, and objects updated after this time (including this time) are not deleted or converted.

Link copied to clipboard
val date: String? = null

Specifies the date after which you want the corresponding action to take effect. The value obeys ISO8601 format like 2017-03-09.

Link copied to clipboard
val days: Int? = null

Specifies the number of days after object creation when the specific rule action takes effect. NOTE: One and only one of "created_before_date" and "days" can be specified in one abort_multipart_upload configuration.

Link copied to clipboard

On a versioned bucket (versioning-enabled or versioning-suspended bucket), you can add this element in the lifecycle configuration to direct OSS to delete expired object delete markers. This cannot be specified with Days, Date or CreatedBeforeDate in a Lifecycle Expiration Policy. NOTE: One and only one of "date", "days", "created_before_date" and "expired_object_delete_marker" can be specified in one expiration configuration.