search

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.17k stars 4.53k forks source link

[Synapse] Remove convenience layer in Azure.Analytics.Synapse.AccessControl #31194

Open wonner opened 1 year ago

wonner commented 1 year ago

Library name

Azure.Analytics.Synapse.AccessControl

Please describe the feature.

The convenience layer in Azure.Analytics.Synapse.AccessControl just initial test work for onboarding to LLC. It's incomplete and abandoned. This convenience layer doesn't release to customers before, so it's safe to remove. In the future, we will consider onboarding to DPG.

related PR: https://github.com/Azure/azure-sdk-for-net/pull/31126

pshao25 commented 1 year ago

@KrzysztofCwalina @tg-msft we added convenience layer before for experimental purpose. Now service team wants to remove them. Could you check out this PR to see if it is OK?

tg-msft commented 1 year ago

Based on the Beta usage numbers at https://www.nuget.org/stats/packages/Azure.Analytics.Synapse.AccessControl?groupby=Version&groupby=ClientName, I think it's fine to make this change.

We should always take these on a case by case basis though because the customer impact of switching from models to protocol only could be very painful if we have a lot of Beta adopters. While the bar to make changes during a Beta is much lower, we still might want to dial conveniences for select champion scenarios or find other ways to minimize pain during the transition.