Customers At the cluster setting level, a user must enable lifecycle policies in the cluster at the cluster setting level. The setting is at the cluster level, so using . As it is enabled in the cluster, so use the management API is appropriate:
| Code Block | ||
|---|---|---|
| ||
curl -X PUT --header 'Content-Type: application/json' --header 'Accept: text/plain' -d '{}'
'http://lucky1.tx.caringo.com:91/api/storage/clusters/_self/settings/policy.lifecycle?value=enabled' -u admin:ourpwdofchoicehere |
| Info |
|---|
...
Do not make any changes because a missing |
A bucket has some lifecycle policies, such as expire :
Expire all versioned content after one year
...
Expire all current content after 5 years, etc.
...
Such policies are applied on a bucket object via one or more Policy-Lifecycle headers:
| Code Block | ||
|---|---|---|
| ||
curl –X COPY –-post301 –-location-trusted –H 'Policy-Lifecycle: RuleId: rule5 ExpirationDays:1825 ObsoleteExpirationDays:365' 'http://lucky1.tx.caringo.com/mybucket?mydomain&preserve' |
In the previous example, we’re not naming the single policy, we are not declaring it enabled (as it is by default), and we are relying on a missing prefix to implicitly apply to all content in the bucket. The preserve query argument on the COPY operations means to leave the other persisted headers as they were.
SeeS3 lifecycle policy examples are also available.