Automate application of s3 expiration rules

RESOLVED FIXED

Status

Cloud Services
Metrics: Pipeline
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: whd, Assigned: relud)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
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).
(Assignee)

Comment 1

2 years ago
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
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.