Planning and Roadmap Feedback - Second Half 2021
See original GitHub issueHello Azure SDK community!
The Azure SDK team is beginning our next planning cycle as part of Azure’s twice a year planning process. As a part of this effort, we want to hear from you about what new features and services you are most interested in having as part of the New SDK. In general, we can separate requests into two categories:
- Feature requests for various aspects of the SDK
- Requests to move Azure services onto the new SDK paradigm
We would love to hear your thoughts on both!
There are three ways you can contribute feedback:
- Browse existing issues labeled
feature-request
in this repository. Use the thumbs up (+1) emoji to give us your indication it’s a high priority for you. - Reply to this issue with comments on new services and features you are looking for.
- Upvote comments in this thread using the thumbs up (+1) emoji.
Note: Being specific with your use case and sample code. The more information you can give us, the more likely we are to take your request.
Please do not create new issues for new service requests - instead, reply inline.
We will be reviewing community feedback and incorporating it into the planning process starting May 10th 2021.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Second Half 2021 · Issue #14559 · Azure/azure-sdk-for-go · ...
Hello Azure SDK community! The Azure SDK team is beginning our next planning cycle as part of Azure's twice a year planning process....
Read more >Exchange Server Roadmap Update
In September 2020, we announced that the next version of Exchange Server would be available in the second half of 2021 via a...
Read more >Second JHU Roadmap on Diversity, Equity, and Inclusion
The Office of Diversity and Inclusion published a draft of the plan in November 2021 and solicited feedback. This final version of the...
Read more >Second Roadmap on DEI—Final report, 24 goals, next steps
Beginning next month and throughout the spring 2022 semester, we will turn in earnest to the development of implementation plans and timelines ...
Read more >Acceleration Roadmap: Pathway to an Equitable Recovery
This roadmap is designed to help educators and administrators plan to accelerate learning for all students during the 2021-2022 school.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I really like the new Azure SDKs, consistent, easy to use, easy to unit test… I would really to have that with the Azure IoT SDK which currently lack these features (unit testing some parts of it is just not possible).
By the way Comos Db SDK v4 has been in preview for a long long time, it would be great to finally see this version released.
thanks.
Hi @maggiepint kudos to the team for all the support. I need a clarification. Assume I have a ton of ARM Templates and I have to deploy them. The deployment happens via REST API from our application.
Take this example on the sample project the main dependency is
Microsoft.Azure.Management.Fluent
But this assembly depends on a lot of other assemblies which I won’t need or use. Is there any other way I can do something like this with any other assembly ?
This causes all these bloated assemblies to be part of our dependencies. Is there any way to avoid this ?