Welcome again to a different launch of the unified Azure Knowledge shopper libraries. For probably the most half, the API floor areas of the SDKs have been stabilized based mostly in your suggestions. Thanks to everybody who has been submitting points on GitHub and preserve the suggestions coming.
Please seize the October preview libraries and take a look at them out—throw demanding efficiency situations at them, combine them with different companies, attempt to debug a problem, or usually construct your situation and tell us what you discover.
Our aim is to launch these libraries earlier than the top of the yr however we’re pushed by high quality and suggestions and your participation is vital.
As we did for the final three releases, we have now created 4 pages that unify all the important thing data it is advisable get began and provides suggestions. You’ll find them right here:
For these of you who need to dive deep into the content material, the discharge notes linked above and the changelogs they level to provide extra particulars on what has modified. Right here we’re calling out a couple of high-level objects.
APIs locking down
The floor space for Azure Key Vault and Storage Libraries are practically API-complete based mostly on the suggestions you’ve given us up to now. Thanks once more to everybody who has despatched suggestions, and if anybody has been ready to strive issues out and provides suggestions, now could be the time.
Batch API help in Storage
The Azure SDKs that rely on Azure Id make getting credentials for companies a lot simpler.
Every library helps the idea of a
DefaultAzureCredential and relying on the place your code runs, it’s going to choose the proper credential for logging in. For instance, when you’re writing code and have signed into Visual Studio or carried out an az login from the CLI, the shopper libraries can mechanically decide up the sign-in token from these instruments. Once you transfer the code to a service surroundings, it’s going to try to make use of a managed identification if one is out there. See the language particular READMEs for Azure Id for extra.
Working with us and giving suggestions
To this point, the neighborhood has filed lots of of points in opposition to these new SDKs with suggestions starting from documentation points to API floor space change requests to mentioning failure instances. Please preserve that coming. We work within the open on GitHub and you may submit points right here:
As well as, we’re excited to say we’ll be attending Microsoft Ignite 2019, so please come and speak to us in individual. Lastly, please tweet at us at @AzureSdk.
Get began with Azure totally free.