Skip to content
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

Open
jiasli opened this issue Nov 22, 2021 · 4 comments · May be fixed by #29631
Open

Drop Track 1 Azure SDK support #20460

jiasli opened this issue Nov 22, 2021 · 4 comments · May be fixed by #29631
Assignees
Labels
Milestone

Comments

@jiasli
Copy link
Member

jiasli commented Nov 22, 2021

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

  • MSAL authentication for Track 1 SDK, including ADAL's resource for backward compatibility
  • Cross-tenant authentication for Track 1 SDK
  • Continuous Access Evaluation for Track 1 SDK
@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Nov 22, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Nov 22, 2021
@yonzhan yonzhan added feature-request needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Nov 22, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Nov 22, 2021
@yonzhan yonzhan added this to the Backlog milestone Nov 22, 2021
@yonzhan yonzhan added the Core CLI core infrastructure label Nov 22, 2021
@jiasli
Copy link
Member Author

jiasli commented Mar 17, 2023

The supportability for deprecated Track 1 SDK adds extra difficulty during the migration to MSAL's managed identity implementation.

@jiasli
Copy link
Member Author

jiasli commented Aug 7, 2023

Track 1 SDKs are causing problems here and there:

  1. azure-keyvault Track 1 data-plane SDK is not compatible with Python 3.11 because of its dependency on deprecated function inspect.getargspec: [Packaging] Support Python 3.11 #26923 (comment)
  2. Installing azure-mgmt-consumption and azure-mgmt-relay Track 1 mgmt-plane SDKs from source code fails with latest wheel because of its dependency on deprecated module wheel.pep425tags: Azure CLI 2.51.0 cannot be released to Homebrew #27047

@virtualjack
Copy link

virtualjack commented Jul 16, 2024

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.

@jsntcy
Copy link
Member

jsntcy commented Jul 26, 2024

Track 1 SDKs are causing problems here and there:

  1. azure-keyvault Track 1 data-plane SDK is not compatible with Python 3.11 because of its dependency on deprecated function inspect.getargspec: [Packaging] Support Python 3.11 #26923 (comment)
  2. Installing azure-mgmt-consumption and azure-mgmt-relay Track 1 mgmt-plane SDKs from source code fails with latest wheel because of its dependency on deprecated module wheel.pep425tags: Azure CLI 2.51.0 cannot be released to Homebrew #27047

azure-mgmt-consumption and azure-mgmt-relay are already migrated to codegen and are not track 1 any longer.

@jiasli jiasli linked a pull request Aug 1, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants