zalando / zalando/postgres-operator
Make backup file names configurable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.14.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s] Bare metal k8s
- Are you running Postgres Operator in production? [yes | no] Yes
- Type of issue? [Bug report, question, feature request, etc.] Feature request
When using logical-backups cronjob it would be useful to be able to change the backup file names from Unix time to something more human readable.
This could allow for better filtering of backups etc.
I propose adding a new env variable for the logical backups that would allow you to change the name generated from $(date +%s) to some other $(date) formats.
I have a PR for this ready that I'm gonna submit later today.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the logical-backups cronjob and the filename generation using $(date +%s), then inspect the related backup configuration and existing tests. Done means the backup filename format can be configured for logical backups and the behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100