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 old Track 2 Azure SDK support #20462

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

Drop old Track 2 Azure SDK support #20462

jiasli opened this issue Nov 22, 2021 · 2 comments · May be fixed by #29690
Assignees
Labels
Core CLI core infrastructure feature-request
Milestone

Comments

@jiasli
Copy link
Member

jiasli commented Nov 22, 2021

#15806 introduced patches for problematic old Track 2 SDKs. As autorest has been updated to generate new SDKs with these bugs fixed:

azure-cli-core should drop these patches as they introduces extra maintenance effort.

@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Nov 22, 2021
@jiasli jiasli changed the title Drop old Track 2 SDK support Drop old Track 2 Azure SDK support Nov 22, 2021
@yonzhan
Copy link
Collaborator

yonzhan commented Nov 22, 2021

Drop old Track 2

@yonzhan yonzhan added the Core CLI core infrastructure 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
@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..

@jiasli jiasli linked a pull request Aug 8, 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
Core CLI core infrastructure feature-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants