Thank you for reading this Azure SDK blog post! We hope that you learned something new and welcome you to share this post. We are open to Azure SDK blog contributions.
Anyone who has worked in software knows that one word that will invoke a whole range of emotions – joy, excitement, perhaps a bit of fear – is planning. Azure iterates continuously on plans, but we have two major planning cycles a year – called semesters. Semester planning is a time during which we work together to re-prioritize community requests and coordinate across teams to deliver the things the community is most excited about. Each semester is named after an element in the periodic table – we are currently in Cobalt and will be moving into Nickel in June. This means May is a BIG month around Azure as we lock our set of Nickel plans.
In the Azure SDK team, we have a unique planning vantage point as we work across all Azure services to deliver a cohesive developer experience. In the past, we have written about the triage process we have in place to distribute GitHub based feedback across Azure teams. Planning is one of the best times to take advantage of this process to help us deliver the developer experience features that the community wants. Over the first two weeks of May, the Azure SDK team will be reviewing community feedback in reactions and comments to get an understanding of what our community want the most, and work with service team partners to get them delivered. This means that the next two weeks are an excellent time to get in your feedback!
For the Nickel planning cycle, we have made some specific “What’s next?” issues for community discussion. Feel free to visit any of these issues and leave comments on what you want to see in the future.
Alternatively, you can raise a feature request in our repos at any time. The Azure SDK team uses the
feature-request label to track these requests. This means that the easiest way to see outstanding requests it to filter to this label in our GitHub repositories.
If an issue has a milestone date listed, then good news – it is already on our backlog!
If it doesn’t, then it’s a great opportunity for you to leave feedback.
In general, we also look for feedback on our design guidelines on a rolling basis – to find proposed changes to design guidelines, look for the tag
There are several ways to leave feedback on Azure SDK GitHub issues. We regularly track the reactions to issues. If you leave us thumbs up (+1), heart, rocket, or hooray on the main issue, we will assume you are interested in the feature being delivered. If you leave thumbs down (-1) or confused on the main issue, we’ll assume you have reservations.
Another way to leave feedback is in the comments! We particularly appreciate comments that describe your specific use case, and give sample code if possible. This helps us get a deeper understanding of the exact capabilities you are looking for, and the gaps we currently have.
Thank you for reading this Azure SDK blog post! We hope that you learned something new and welcome you to share this post. We are open to Azure SDK blog contributions. Please contact us at [email protected] with your topic and we’ll get you set up as a guest blogger.
In this post we will learn about Azure SDK for Java application and HTTP logging scenarios in an Azure Functions environment. We will look at the scenario of managing secrets in the Azure Key Vault with the Key Vault and Identity client libraries and how to activate and access the SDK logs in the Azure Functions environment.
We’ll read about the Android SDK Manager. We will see what is SDK manager in Android and why and how it is important for Android
Since we shipped the first Azure Identity library preview in June 2019, it has been a vital part of building Azure cloud solutions. We have received great feedback from our development community and have added new features and have fixed many bugs.
In this article, see how to programmatically manage Azure Data Explorer resources using Go.Getting started with Azure Data Explorer using the Go SDK covered how to use the Azure Data Explorer Go SDK to ingest and query data from azure data explorer to ingest and query data. In this blog you will the Azure Go SDK to manage Azure Data Explorer clusters and databases.