obs_lifecycle_conf
| Parameter | Type | Mandatory (Yes/No) | Description |
|---|---|---|---|
| date | const char * | Yes if there is no days and no transition, noncurrent_version_days, or noncurrent_version_transition | Explanation: When the object expiration rule of the latest version takes effect. The value must conform to the ISO8601 standard and indicate 00:00:00 in UTC. Restrictions: None Value range: None Default value: None |
| days | const char * | Yes if there is no date and no transition, noncurrent_version_days, or noncurrent_version_transition | Explanation: Number of days when the expiration rule takes effect after the object creation (only applicable to the latest version of an object). Restrictions: None Value range: None Default value: None |
| id | const char * | No | Explanation: Unique identifier of a rule. The value can contain a maximum of 255 characters. Restrictions: None Value range: None Default value: None |
| prefix | const char * | Yes | Explanation: Object name prefix. It identifies the objects the rule applies to. Restrictions: None Value range: None Default value: None |
| status | const char * | Yes | Explanation: Whether the rule is enabled Restrictions: None Value range:
Default value: None |
| noncurrent_version_days | const char * | No | Explanation: Container for the expiration time of objects' historical versions. If versioning is enabled or suspended for a bucket, you can set this parameter to delete historical versions of objects that match the lifecycle rule. Restrictions: This parameter is only available for historical object versions. Value range: None Default value: None |
| transition | obs_lifecycle_transition * | Yes if there is no date, days, noncurrent_version_transition, or noncurrent_version_days | Explanation: The transition time and the object storage class after transition (valid only for the latest object version). Restrictions: None Value range: None Default value: None |
| transition_num | unsigned int | Yes if transition is specified | Explanation: Number of array members in the transition array. Restrictions: None Value range: None Default value: None |
| noncurrent_version_transition | Table 3 * | Yes if there is no date, days, transition, or noncurrent_version_days | Explanation: Transition time of historical object versions and the object storage class after transition. Restrictions: None Value range: None Default value: None |
| noncurrent_version_transition_num | unsigned int | Yes if noncurrent_version_transition is specified | Explanation: Number of array members in the array noncurrent_version_transition. Restrictions: None Value range: None Default value: None |
| Parameter | Type | Mandatory (Yes/No) | Description |
|---|---|---|---|
| date | const char * | Yes if the obs_lifecycle_transition.days element is absent | Explanation: When the object expiration rule of the latest version takes effect. The value must conform to the ISO8601 standard and indicate 00:00:00 in UTC. Restrictions: None Value range: None Default value: None |
| days | const char * | Yes if the obs_lifecycle_transition.date element is absent | Explanation: Number of days when the expiration rule takes effect after the object creation (only applicable to the latest version of an object). Restrictions: None Value range: None Default value: None |
| storage_class | Yes | Explanation: The storage class to which the latest object version will be changed Restrictions: None Value range: None Default value: None |
| Parameter | Type | Mandatory (Yes/No) | Description |
|---|---|---|---|
| noncurrent_version_days | const char * | Yes | Explanation: Number of days an object is historical before the specified transition rule takes effect Restrictions: This parameter is only available for historical object versions. Value range: None Default value: None |
| storage_class | Yes | Explanation: The storage class to which historical versions will be changed Restrictions: None Value range: None Default value: None |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot