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

Azure has switched to using a new SDK #1684

Closed
bathina2 opened this issue Oct 14, 2022 · 4 comments
Closed

Azure has switched to using a new SDK #1684

bathina2 opened this issue Oct 14, 2022 · 4 comments

Comments

@bathina2
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The SDK we currently use is deprecated and we should switch to using the new azure SDK. This will take some work since some there are several changes.
Copied from sdk-
Deprecated: Please note, this package has been deprecated. A replacement package is available [github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute]([https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html)). We strongly encourage you to upgrade to continue receiving updates. See [Migration Guide]([https://aka.ms/azsdk/golang/t2/migration](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html)) for guidance on upgrading. Refer to our [deprecation policy]([https://azure.github.io/azure-sdk/policies_support.html](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html)) for more details.

Describe the solution you'd like
Switch over to using the new azure sdk

@github-actions
Copy link
Contributor

Thanks for opening this issue 👍. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

@pavannd1 pavannd1 removed the triage label Nov 9, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jan 9, 2023

This issue is marked as stale due to inactivity. Add a new comment to reactivate it.

@github-actions github-actions bot added the stale label Jan 9, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2023

This issue is closed due to inactivity. Feel free to reopen it, if it's still relevant.

@pavannd1
Copy link
Contributor

Duplicates #1568.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants