Correctly handle blob MD5 sums in custom blob resource, need to be base64-encoded#3718
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
danielrbradley
left a comment
There was a problem hiding this comment.
Change looks good. Would be good to have an integration test for the blobs running ahead of merge at some point.
Options I can see here:
- Assuming you've run the test locally, that should suffice for now.
- We could also do a manual CI run for the branch to include all tests.
- We could also unmark one of the integration tests with
skipIfShortso it's always run. - Or we should introduce a merge queue so it only merges after the full integration test suite has run.
7065148 to
3f70285
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3718 +/- ##
==========================================
- Coverage 56.31% 56.30% -0.02%
==========================================
Files 74 74
Lines 11735 11738 +3
==========================================
Hits 6609 6609
- Misses 4635 4638 +3
Partials 491 491 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
I ran the full test suite via |
|
This PR has been shipped in release v2.73.0. |
This was initially missed because the previously used Azure SDK in custom_storage.go, and the newer one used in custom_storage_azidentity.go, behave differently. The older SDK leaves the user-provided MD5 sum alone, so the user needs to provide it base64-encoded, as the integration test examples/static-website/index.ts does. The newer SDK, however, expects the MD5 sum as a raw byte array and does the base64-decoding internally. Providing an already encoded sum leads to double-encoding and an invalid sum being sent to Azure.