Azure / azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.47k stars 4.8k forks source link

Why does the DataLakeServiceClient not support connection strings when all other clients do? #15259

Closed sonic1981 closed 8 months ago

sonic1981 commented 4 years ago

Describe the bug The overloads for the DataLakeServiceClient does not have an overload that accepts a connection string.

All the other clients (.e.g. BlobContainerClient) do have a connection string overload.

Expected behavior Expose an overload for the DataLakeServiceClient constructor that accepts a connection string.

Actual behavior (include Exception or Stack Trace) You currently only have the option of using a URI. This requires the setting up of additional IAM permissions and is inconsistent with the other providers.

Environment:

jsquire commented 4 years ago

Thank you for your feedback. Tagging and routing to the team best able to assist.

ghost commented 4 years ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sumantmehtams.

sonic1981 commented 4 years ago

This is tagged incorrectly @jsquire I'm referring to Data Lake Storage Gen 2 not Gen 1 :)

jsquire commented 4 years ago

Thanks, @sonic1981. My mistake during selection; the good news is that it routes to the same team. :smile:

ghost commented 4 years ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sumantmehtams.

Marusyk commented 3 years ago

any updates?

lawrencegripper commented 3 years ago

Would it be possible to make the StorageConnectionString public, this way users could pull in Azure.Storage.Common and call

public static StorageConnectionString Parse(string connectionString)

Then pass the required results to the DataLakeClient?

ghost commented 3 years ago

Hi @sonic1981. Thank you, for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

sonic1981 commented 3 years ago

This still hasn't been looked at by anyone

JimSuplizio commented 8 months ago

Hi @sonic1981, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.