Add snapshot-based ETL workflow - #10
Closed
matthewpeterkort wants to merge 1 commit into
Closed
Conversation
matthewpeterkort
marked this pull request as ready for review
August 6, 2026 22:00
matthewpeterkort
force-pushed
the
reliability/federation
branch
from
August 6, 2026 22:52
ae9f1f4 to
1e6a3bd
Compare
matthewpeterkort
force-pushed
the
reliability/etl
branch
from
August 6, 2026 22:52
7d39a8e to
d76e291
Compare
Contributor
Author
|
Closing: the ETL pod has its own client; the optional pkg/loometl SDK is being removed from this stack. |
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
1 participant
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\n\nUpdates the ETL client to use immutable Git-keyed snapshots, checksum-verified uploads, exact-version materialization polling, release activation gating, structured diagnostics, safe retries, and legacy-upload rollout controls.\n\n## Stack\n\nFifth tier; depends on reliability/federation.\n\n## Validation\n\nETL acceptance tests cover network loss at every step, idempotent retries, checksum failures, publication diagnostics, release preservation, and terminal activation confirmation.