Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Storage blob versioning #1229

Open
MariuszBartnik opened this issue Dec 20, 2024 · 0 comments
Open

Azure Storage blob versioning #1229

MariuszBartnik opened this issue Dec 20, 2024 · 0 comments
Labels

Comments

@MariuszBartnik
Copy link

I have a Azure Storage account with blob versioning functionality enabled. I want to upsert file, by providing the same path for blob as the one, that already exists on the storage and create a new version of this file in this way. I was doing this without any problems on my previous setup, which was an Express app with multer streaming files to Azure, but now I want to migrate to using tusd instead.

I have noticed an issue with this approach though. When I try to download the updated file I am still getting the original one, instead of a new one, even if the upload was a success. I've notice that the issue is connected to this piece of code in the getOffset function in azureservice.go file.

getBlock, err := blockBlob.Blob.GetBlockList(ctx, azblob.BlockListAll, azblob.LeaseAccessConditions{})

I might be missing something, so I wanted to ask if we really need to get the block list for azblob.BlockListAll instead of azblob.BlockListUncommitted? With this setup function is returning blocks for both files - updated and original.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant