-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Drop Track 1 Azure SDK support #20460
Comments
The supportability for deprecated Track 1 SDK adds extra difficulty during the migration to MSAL's managed identity implementation. |
Track 1 SDKs are causing problems here and there:
|
Bump For the company that I work for, a financial institution, the use of the ADAL package which per Microsoft is no longer receiving security patches as of December 2022 is a significant problem. We can't use software that no longer receives security updates per our customers (& regulators). Remove the MS containers in AKS that leverage az-cli would be a significant effort (mcr.microsoft.com/oss/kubernetes/azure-cloud-node-manager, mcr.microsoft.com/oss/kubernetes-csi/azurefile-csi, mcr.microsoft.com/azuredefender/stable/low-level-collector, mcr.microsoft.com/oss/azure/secrets-store/provider-azure). Let me know if there is a manager at MS that my company should reach out to in order to ensure that this ticket gets sufficient resources and not be de-prioritized by other management. |
|
As Track 1 Azure SDK has been deprecated and out of maintenance (public announcement?),
azure-cli-core
needs to drop Track 1 SDK support.The extended Track 1 SDK support in MSAL-based Azure CLI adds tons of extra maintenance effort for
resource
for backward compatibilityThe text was updated successfully, but these errors were encountered: