refactor(backup): bundle WAL-G with PostgreSQL image - #187
Merged
Merged
Conversation
vishr
force-pushed
the
feat/postgres-walg-image
branch
2 times, most recently
from
September 14, 2026 14:37
bd47bd9 to
ed1b177
Compare
vishr
force-pushed
the
feat/postgres-walg-image
branch
from
September 14, 2026 14:44
ed1b177 to
7f999b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
onebox-postgres:18imageImage contract
onebox-postgres:18remains the single curated PostgreSQL runtime. Its contents include PostgreSQL extensions and WAL-G; WAL-G is not a separate image variant or tag.Live-test fixes
RepoDigestslist instead of trusting list orderVerification
just docs-generate-checkjust workflow-checkgo test ./...(2,030 passed)wal-g --version, and final-image check for WAL-G/CA roots with no Go runtimeTestServerProbespassed in 434.7s against the exact locally built image served from a VM-local registry, including enablement, WAL archiving, base backup, generation recovery, repeat enablement, and teardown