zalando / zalando/postgres-operator
WAL*_S3_PREFIX missing version in /run/etc/wal-e.d/env-clone-*
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. registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS K8s | Azure
- Type of issue? Bug report
Original env looks like this:
s3://<s3 bucket>/spilo/<database>/<UID>/wal/13
env-clone-* though is missing the version at the end:
s3://<s3 bucket>/spilo/<database>/<UID>/wal
I have confirmed that this does break the restore process. Manually appending the version in the image fixes this specific issue. Unfortunately, I don't think there's a way to add environment variables via pod-env-override to get the restore to work though.
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 tracing how /run/etc/wal-e.d/env-clone-* is generated and compare its WAL_S3_PREFIX with the original environment. Reproduce the clone restore on AWS Kubernetes and verify that the generated prefix includes the PostgreSQL version, then confirm the restore completes without manual edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100