Versions Compared

Version Old Version 7 New Version Current
Changes made by

Donald Baker (Deactivated)

Jamshid Afshar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

At the cluster setting level, a A user must enable lifecycle policies . As it is enabled in at the cluster , so use setting level. Use the management API when enabled:

Code Block
languagebash
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

Info

A missing Policy-Lifecycle header on the domain is considered a tacit enablement so it is not required to make that does not require any changes.

A bucket may have contains one or multiple lifecycle policies, such as:

  • Expire all versioned content after one year.

  • Expire all current content after 5 years, etc.

...

Code Block
languagebash
curl –X-X COPY –--post301 –--location-trusted –H \
    -H 'Policy-Lifecycle: RuleId:"rule5" ExpirationDays:1825 ObsoleteExpirationDays:365' \
    'http://lucky1.tx.caringo.com/mybucket?domain=mydomain&preserve'

In the previous example, apply implicitly applying to all content in the bucket by;:

  • Naming the single policy

  • Not declaring it enabled (as it is by default enabled)

  • Relying on a missing prefix

The preserve query argument on the COPY operations indicates leaving other persisted headers as it is.SeeS3 lifecycle policy examples. Note that Swarm currently only supports expiration policiesunchanged.

Info

Important

  • Re-transmit all Policy-Lifecycle headers to appear on the new object. It is advised to use the Content UI for editing policy rules.

  • Swarm supports expiration policies currently.

Seehttps://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html.