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.
Contrary to the closed #3012 the cli auth didn't work for me so I've taken a look a made a working version.
However! Here https://github.com/google/go-cloud/blob/master/blob/azureblob/azureblob.go#L42 it says it should fall back to
NewDefaultAzureCredentials
but I don't see it happening in the code below.But then again after looking at https://github.com/Azure/azure-sdk-for-go/blob/sdk/azidentity/v1.1.0/sdk/azidentity/default_azure_credential.go#L45-L93 it seems it does something similar as code here https://github.com/google/go-cloud/blob/master/blob/azureblob/azureblob.go#L320-L331 so maybe we should just use
NewDefaultAzureCredentials
straight away?Hence, I'm creating this PR as a draft to discuss the approach first.