Closed Bug 1210972 Opened 9 years ago Closed 9 years ago

Automate application of s3 expiration rules

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whd, Assigned: relud)

Details

Our prod bucket predates CFN management, so we can't use the mechanism :relud implemented that I attempted to update in https://github.com/mozilla-services/svcops/pull/681.

:relud is going to work on setting this up via ansible instead. As part of this, we'd like to additionally add to the top level sources.json the expiration policy (this in effect means sources.json will be version controlled).
https://github.com/mozilla-services/svcops/pull/709 fixed the method for managing s3 buckets to handle existing buckets.

sources.json was left alone.
Assignee: nobody → dthorn
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.