cloudnative-pg / cloudnative-pg/plugin-barman-cloud

S3 lifecycle policy and history files

Ouverte
#779 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
question
Langage dominant
Go
Étoiles
191
Forks
72
Merge moyen
2 j 21 h
PR mergées (30 j)
21

Description

This is more like a general question about S3 lifecycle policies, since there is some conflicting information about this topic. The docs (https://cloudnative-pg.io/plugin-barman-cloud/docs/object_stores/#s3-lifecycle-policy) explicitly recommend setting an S3 lifecycle policy on the current versions of the objects as well. However, this would also expire history files, which are not touched in the objectstore after transfering them once. Are these archived history files not needed for restoration? Then why archive them? If they are needed, then is there some mechanism that guarantees a timeline switch in each retention window?

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start with the S3 lifecycle policy section linked in the issue and trace how archived history files are used during restoration. Confirm whether the documented lifecycle recommendation can expire them safely and whether a timeline switch is guaranteed within each retention window. Done means resolving the questions and updating the documentation with an unambiguous explanation.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
aws, postgresql
Domaine
cloud, databases, documentation
Type d'issue
Documentation
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.