-
Notifications
You must be signed in to change notification settings - Fork 69
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
Upgraded azure storage blob to 0.14.0 #237
Conversation
Not sure who could take a look here. We have a pretty bad dependency lock in our project due to this. Would be awesome to get that in. |
@Nighthawk22 - I am sorry I missed this one. I'm taking a look at it now. |
Just a little status update - there are some issues with the latest storage library and how we're doing authentication internally, so all the live tests using this are failing. Still looking at it. |
Hi @Nighthawk22, looking at this some more there are a few issues with moving to a newer version of the Storage-Blob package. We'll need to take a look at this in the nearer future. The other complication is that I'm not able to reproduce the issue that spawned this bug in the first place, so it's not entirely clear if the update will fix it (unfortunately). |
Closing for now as I don't think we can merge it until we get the storage plan in place. |
Fix or Enhancement?
Fix of compatible to most recent azure blob storage version.
Fixes #228
changelog.md
Breaks compatibility with older azblob versions.
TBD
Should it be possible to provide the customer provided keys? Currently they are neglected.
Environment