-
Notifications
You must be signed in to change notification settings - Fork 152
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
Update Azure SDK Libraries before March 2023 #1568
Comments
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. |
@leuyentran Thank you for pointing this out 🙏🏼 |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
Relevant |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
This issue is closed due to inactivity. Feel free to reopen it, if it's still relevant. |
@pavannd1 Any plans to do this soon? |
We'll triage this soon 💯 |
go-autorest
being used in theblockstorage
package will be out of support from March 2023. Follow the documentation below to replace it with a new supported package.https://azure.microsoft.com/en-us/updates/support-for-azure-sdk-libraries-that-do-not-conform-to-our-current-azure-sdk-guidelines-will-be-retired-as-of-31-march-2023/
The new libraries can be found here: https://azure.github.io/azure-sdk/
The text was updated successfully, but these errors were encountered: