feat: implement blob versioning support - #2689
Draft
jainakanksha-msft with Copilot wants to merge 2 commits into
Draft
feat: implement blob versioning support#2689jainakanksha-msft with Copilot wants to merge 2 commits into
jainakanksha-msft with Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Enable blob versioning for Azurite testing
feat: implement blob versioning support
Aug 3, 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
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.
Azurite had no support for Azure Blob Storage versioning — overwriting a blob should preserve the previous content as a named version accessible by
versionId. This adds versioning lifecycle support to the Loki-backed blob metadata store.Model & XML Serialization
BlobVersioninginterface ({ enabled?: boolean }) and replaced the flatisVersioningEnabledfield onStorageServicePropertieswith a properversioning?: BlobVersioningcomposite fieldBlobVersioningcomposite mapper so<Versioning><Enabled>true</Enabled></Versioning>round-trips correctly via msrest XML serializationMetadata Store (
LokiBlobMetadataStore)createBlob/commitBlockList: when versioning is enabled, marks the existing blob asisCurrentVersion: false(instead of deleting) and inserts the new blob with a freshversionIdandisCurrentVersion: truegetBlobWithLeaseUpdated: accepts optionalversionIdfor direct version lookup; without it, filters outisCurrentVersion === falseblobs so non-versioned callers are unaffectedlistBlobs: addedincludeVersionsflag; whenfalse(default), previous versions are hiddendeleteBlob: whenversionIdis specified, removes only that versionHTTP Handlers
BlobHandler/BlockBlobHandler: propagateversionIdoption into store calls and surfaceversionId/isCurrentVersionin responsesContainerHandler: parsesinclude=versionsfrom list requests and passesincludeVersionstolistBlobs; emitsversionId/isCurrentVersionper blob itemUsage example