Repository navigation
feat(events-processor): add Dockerfile.staging for hardened build path - #804
Merged
Merged
Conversation
Restores the hardened staging build for events-processor, FROMing the Wolfi/apko bases now published by getlago/lago-packages to GHCR. This supersedes #800 rather than continuing it. That branch was force-pushed onto main before being closed, so it holds no changes and GitHub will not reopen it. Unlike lago-front#4318 no review was pinned to the pre-push commit, so the original is unrecoverable; this is adapted from the copy that lives in lago-deploy#3331. That copy sat in the private lago-deploy repo specifically to keep ECR URLs and the AWS account id out of a public repository. The bases are public on GHCR now, so the Dockerfile can live beside the code it builds, as lago-api's already does. Build logic is unchanged — the context is still this directory, so COPY paths behave exactly as before. The sibling ./Dockerfile still serves production.
vincent-pochet
approved these changes
Sep 18, 2026
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
2 participants
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.
Restores the hardened staging build for
events-processor, FROMing the Wolfi/apko bases now published by getlago/lago-packages to GHCR.Why this is a new PR and not #800 reopened
#800 cannot be reopened. Its branch was force-pushed onto
mainat the moment it was closed, so it now contains no changes and GitHub refuses to reopen a PR with an empty diff.Unlike lago-front#4318 — where a pinned review preserved the pre-push commit — nothing in #800's timeline references its original head, so that version is genuinely gone. This is adapted from the copy in lago-deploy#3331, which is the same work.
Why the Dockerfile lives here
lago-deploy#3331 put this file in the private
lago-deployrepo, stating:Sound while the bases were in ECR; obsolete now. The bases are public on GHCR, so there is no account id or private registry reference to hide, and pulling them needs no credentials.
Build logic unchanged
The paired workflow already sets the build context to
events-processor/, soCOPY . /app/resolves exactly as before — only the Dockerfile's location and the twoARGdefaults change. The Rust FFI dependency is still pinned toLAGO_EXPRESSION_REF=v0.2.0to match the production./Dockerfile; bump both together.Companion changes
events-processor-base/events-processor-build— both green, public, multi-arch, cosign-signedNot in this PR
events-processor/Dockerfileis untouched and continues to serve production builds.