Add SHA256 checksum storage for ActiveStorage blobs#663
Draft
dmitrytrager wants to merge 1 commit intomainfrom
Draft
Add SHA256 checksum storage for ActiveStorage blobs#663dmitrytrager wants to merge 1 commit intomainfrom
dmitrytrager wants to merge 1 commit intomainfrom
Conversation
Device sync protocol requires SHA256-prefixed per-file checksums so Clinical Edge can verify downloaded files against the manifest. Adds a sha256_checksum column to active_storage_blobs, async calculation via Blobs::ComputeSha256ChecksumJob on blob creation, a lazy fallback for legacy blobs, and a backfill rake task. ManifestBuilder now emits sha256:<digest> per the data-exchange spec. Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
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.
What Issue Does This PR Cover, If Any?
Resolves #574
What Changed? And Why Did It Change?
Device sync protocol requires SHA256-prefixed per-file checksums so Clinical Edge can verify downloaded files against the manifest. Adds a sha256_checksum column to active_storage_blobs, async calculation via Blobs::ComputeSha256ChecksumJob on blob creation, a lazy fallback for legacy blobs, and a backfill rake task. ManifestBuilder now emits sha256: per the data-exchange spec.
How Has This Been Tested?
Please Provide Screenshots
Additional Comments