FromConnectionString method for StorageSharedKeyCredential
See original GitHub issueLibrary or service name. Azure.Storage.Common
Is your feature request related to a problem? Please describe.
It looks like StorageSharedKeyCredential
should have a static FromConnectionString
method. The Java library has one:
Thanks
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
StorageSharedKeyCredential Class
Method Summary Creates a SharedKey credential from the passed connection string. Generates the SharedKey Authorization value from information in the request.
Read more >Why there is no StorageSharedKeyCredential. ...
Set the variables in environment and read it from there. (redundancy) · Extract the fromConnectionString parser and use it as a helper function....
Read more >Uses of Class com.azure.storage.common ...
Creates a SharedKey pipeline policy that adds the SharedKey into the request's authorization header. Uses of StorageSharedKeyCredential in com.azure.storage.
Read more >How to use the @azure/storage-blob.BlobServiceClient. ...
fromConnectionString function in @azure/storage-blob. To help you get started, we've selected a few @azure/storage-blob examples, based on popular ways it ...
Read more >Access blob by URI using Storage Connection String in C# ...
I'm using the Azure.Storage.Blobs SDK version 12.7 in C# with .net core and I want to access a blob directly by it's URI...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @j055, this seems like a reasonable suggestion, we will look into adding it to the SDK soon.
Hi @j055. There was a mistake and this issue was unintentionally flagged as a stale pull request. The label has been removed and the issue will remain active; no action is needed on your part. Apologies for the inconvenience.