At the cluster setting level, a user must enable lifecycle policies. As it is enabled in the cluster, so use the management API:
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
Do not make any changes because a missing Policy-Lifecycle header on the domain is considered a tacit enablement.
A bucket has some lifecycle policies, such as:
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:
curl –X COPY –-post301 –-location-trusted –H 'Policy-Lifecycle: RuleId: rule5 ExpirationDays:1825 ObsoleteExpirationDays:365' 'http://lucky1.tx.caringo.com/mybucket?domain=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.