Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Annual rotation of S3 backups #53

Open
jpmckinney opened this issue Oct 27, 2020 · 0 comments
Open

Annual rotation of S3 backups #53

jpmckinney opened this issue Oct 27, 2020 · 0 comments
Labels
storage Relating to S3

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Oct 27, 2020

Per the Google Doc #50:

https://ocdsdeploy.readthedocs.io/en/latest/use/kingfisher-process.html#data-retention-policy says that once we start on the current year, we go back to older years and only keep one per year (the first in that year)

This process should be manually run annually.

A management command can be written to interact with S3 and give the user the information needed to decide which backups to keep, following the retention policy. This can be a simple command-line interface.

See the notes below the horizontal rule in this comment (e.g. about different logic for Digiwhist): open-contracting/deploy#153 (comment)

@jpmckinney jpmckinney added the storage Relating to S3 label Oct 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
storage Relating to S3
Projects
None yet
Development

No branches or pull requests

1 participant