-
-
Notifications
You must be signed in to change notification settings - Fork 376
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 SDK for Go DEPRECATED #1290
Comments
@neolynx , @chuan , @randombenj , @lbolla , @andrewshadura - Apologies for all the tags, but wasn't sure who would be most appropriate. It looks like we have an incoming breaking change soon for the newly added Azure support. Does anyone have cycles to take a look? |
Thanks for reporting !! as I don't really have azure storage access, I would need some help with that.. would you be able to prepare a pull request ? |
@neolynx Hi there! Do you still need access to an Azure storage instance to test this? Or I read elsewhere that you would like to stay on a particular Go version. |
the go version has been updated to 1.22.7 ! would that be suitable for the new Azure SDK ? yes, if you could help with testing Azure (i.e. have a test account) that would be great. I had a free tier, but it expired.. |
also, aptly uses https://github.com/potatoqualitee/azuright 1.1 for testing azure. but there seems to be no newer version. it would be greate somehow if the new sdk could be emulated for testing. do you think this is already possible with 1.1 ? |
The library https://github.com/Azure/azure-storage-blob-go/ that aptly uses to deploy packages to Azure is deprecated and will be retired 2024-09-13. As described there, it should be replaced with https://github.com/Azure/azure-sdk-for-go before that date.
Comparing the old azblob SDK documentation https://pkg.go.dev/github.com/Azure/azure-storage-blob-go/azblob and the new azblob SDK documentation https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob, it does not appear to be a drop-in replacement.
The text was updated successfully, but these errors were encountered: