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

S3 lifecycle policy and history files

Open
#779 1 comment 0 reactions 0 assignees View on GitHub
question
Dominant language
Go
Stars
191
Forks
72
Avg merge
2d 21h
Merged PRs (30d)
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?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.