Get Bucket Lifecycle Rule Condition
Constructors
Properties
Creation date of an object in RFC 3339 (e.g. 2017-06-13) to satisfy this condition.
Creation date of an object in RFC 3339 (e.g. 2017-06-13) to satisfy this condition.
Number of days elapsed since the user-specified timestamp set on an object.
Number of days elapsed since the noncurrent timestamp of an object. This condition is relevant only for versioned objects.
One or more matching name prefixes to satisfy this condition.
Storage Class of objects to satisfy this condition. Supported values include: MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, DURABLE_REDUCED_AVAILABILITY.
One or more matching name suffixes to satisfy this condition.
Creation date of an object in RFC 3339 (e.g. 2017-06-13) to satisfy this condition.
Relevant only for versioned objects. The number of newer versions of an object to satisfy this condition.
While set true, age value will be sent in the request even for zero value of the field. This field is only useful for setting 0 value to the age field. It can be used alone or together with age.
While set true, days_since_custom_time value will be sent in the request even for zero value of the field. This field is only useful for setting 0 value to the days_since_custom_time field. It can be used alone or together with days_since_custom_time.
While set true, days_since_noncurrent_time value will be sent in the request even for zero value of the field. This field is only useful for setting 0 value to the days_since_noncurrent_time field. It can be used alone or together with days_since_noncurrent_time.
While set true, num_newer_versions value will be sent in the request even for zero value of the field. This field is only useful for setting 0 value to the num_newer_versions field. It can be used alone or together with num_newer_versions.