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

internal/build: switch azure sdk from Azure/azure-storage-blob-go to Azure/azure-sdk-for-go/sdk/storage/azblob. #24473

Merged
merged 5 commits into from
Mar 2, 2022

Conversation

uji
Copy link
Contributor

@uji uji commented Feb 27, 2022

updated Azure/azure-storage-blob-go from v0.7.0 to v0.14.0(latest version).

executed following command.

go get -u azure-storage-blob-go
go mod tidy

and then, fixed for breaking changes of Azure/azure-storage-blob-go.

relation #24396.

update Azure/azure-storage-blob-go from v0.7.0 to v0.14.0.
relation ethereum#24396.
@uji uji marked this pull request as draft February 27, 2022 06:55
fix for breaking changes of update Azure/azure-storage-blob-go from v0.7.0 to v0.14.0.
relation ethereum#24396.
@uji uji changed the title go.mod: update azure-storage-blob-go internal/build: update azure-storage-blob-go Feb 27, 2022
@uji uji marked this pull request as ready for review February 27, 2022 07:58
@karalabe
Copy link
Member

karalabe commented Mar 1, 2022

Thanks for the PR! Reading up a bit on the Azure SDK's though, it seems that https://github.com/Azure/azure-storage-blob-go has been deprecated last year and everyone is advised to switch to https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob. Perhaps it would be wiser to do the jump in one go rather than switching to a version we know is not supported any more.

@uji uji force-pushed the azure-storage-blob-go@v0.14.0 branch from 130d742 to 60e1166 Compare March 1, 2022 17:24
@uji uji changed the title internal/build: update azure-storage-blob-go internal/build: switch azure sdk from Azure/azure-storage-blob-go to Azure/azure-sdk-for-go/sdk/storage/azblob. Mar 1, 2022
@uji
Copy link
Contributor Author

uji commented Mar 1, 2022

@karalabe
Copy link
Member

karalabe commented Mar 2, 2022

Fixed some panics due to missing container ID from the URL (previously there were set in dedicated function calls which you removed). LGTM

@karalabe karalabe merged commit 8fddf27 into ethereum:master Mar 2, 2022
@karalabe karalabe added this to the 1.10.17 milestone Mar 2, 2022
JacekGlen pushed a commit to JacekGlen/go-ethereum that referenced this pull request May 26, 2022
…Azure/azure-sdk-for-go/sdk/storage/azblob. (ethereum#24473)

* go.mod: update azure-storage-blob-go

update Azure/azure-storage-blob-go from v0.7.0 to v0.14.0.
relation ethereum#24396.

* internal/build: fix for breaking changes of azure-storage-blob-go

fix for breaking changes of update Azure/azure-storage-blob-go from v0.7.0 to v0.14.0.
relation ethereum#24396.

* internal/build: switch azure sdk from Azure/azure-storage-blob-go to Azure/azure-sdk-for-go/sdk/storage/azblob.

* internal/build refactor appending BlobItems

* internal/build: fix azure blobstore client to include container id

Co-authored-by: Péter Szilágyi <peterke@gmail.com>
cp-wjhan pushed a commit to cp-yoonjin/go-wemix that referenced this pull request Nov 16, 2022
…Azure/azure-sdk-for-go/sdk/storage/azblob. (ethereum#24473)

* go.mod: update azure-storage-blob-go

update Azure/azure-storage-blob-go from v0.7.0 to v0.14.0.
relation ethereum#24396.

* internal/build: fix for breaking changes of azure-storage-blob-go

fix for breaking changes of update Azure/azure-storage-blob-go from v0.7.0 to v0.14.0.
relation ethereum#24396.

* internal/build: switch azure sdk from Azure/azure-storage-blob-go to Azure/azure-sdk-for-go/sdk/storage/azblob.

* internal/build refactor appending BlobItems

* internal/build: fix azure blobstore client to include container id

Co-authored-by: Péter Szilágyi <peterke@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants