This Prefix can be empty if you want a rule to apply to all files in a bucket.Ī string value describing the status of the lifecycle policy. For example, objects that begin with error_report- could be targeted for deletion by providing this prefix. This string is used to select objects for deletion with the same matching prefix. If one is not specified in your policy file, then a random alphanumeric ID will be assigned to your policy when the policy is applied to a bucket.Ī Lifecycle rule can apply to all or a subset of objects in a bucket based on the element that you specify in the Lifecycle rule.You can filter objects by key prefix, object tags, or a combination of both. If your lifecycle policy contains multiple rules, then the ID for each should be unique. It’s also a good idea to include an ID block: Blockĭefines a name for the lifecycle policy rule. The Rule block must contain Prefix and Status, and at least one action, like the Expiration block. Each lifecycle policy file needs a LifecycleConfiguration block and a nested Rule block. The above lifecycle policy deletes all objects in the bucket after one day. This means that if you set a lifecycle policy of one day, the objects will be deleted the midnight after they become 24 hours old. Lifecycle policies are triggered starting at midnight of the Object Storage cluster’s local time.
Cyberduck version 4.5 how to#
When policies are enforced and will then explain how to create and delete lifecycle policies with two tools: This is useful for cases where the data in a bucket becomes outdated, such as when collecting activity logs.
For instance, you can create a lifecycle policy that deletes objects every thirty days, or once a week. Policies are sets of rules that govern the management of objects after they have aged for a certain amount of time. A lifecycle policy is applied to a bucket.
0 kommentar(er)
