#azuresdk — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #azuresdk, aggregated by home.social.
-
Azure Developer CLI (azd) – February 2026: JMESPath Queries & Deployment Slots
https://devblogs.microsoft.com/azure-sdk/azure-developer-cli-azd-february-2026/
-
What’s new in Microsoft Foundry | Dec 2025 & Jan 2026 | by Nick Brady
https://devblogs.microsoft.com/foundry/whats-new-in-microsoft-foundry-dec-2025-jan-2026/
#ai #azure #foundry #agents #models #microsoftfoundry #azuresdk
-
Azure Developer CLI (azd) – October 2025
https://devblogs.microsoft.com/azure-sdk/azure-developer-cli-azd-october-2025/
-
Azure Developer CLI (azd) – May 2025.
https://devblogs.microsoft.com/azure-sdk/azure-developer-cli-azd-may-2025/?hide_banner=true
-
Look. I get it. You don't want to make an `enum` for your constrained string values collection so you make it a `struct` instead.
But for the love of got, then, make it implicitly convertible to a string. (or, did you know there's an `EnumMember` attribute? even better!)
I'm looking at you #AzureSDK folks.
-
Rust in time! Announcing the Azure SDK for Rust Beta. 🎉
-
Azure SDK Release (November 2024).
https://buff.ly/413PVbz
#cloud #azure #azuresdk #dotnet #java #javascript #python #golang -
Prototyping test recording for #AzureSDK for #RustLang: https://github.com/heaths/recorded-tests
Attribute sync or async tests using `#[recorded]` and can accept optional `TestContext` parameter. Full implementation should automatically set up HTTP transport to record or play back.
Thoughts? Still early.
-
TIL that the azure-mgmt-core library (#AzureSDK for #Python) actually contains some useful helper functions:
- parse_resource_id(), which returns the parts of the id
- resource_id(), which builds a resource id based on the parameters passed into the function
- is_valid_resource_id(), to validate a resource id
- is_valid_resource_name(), to validate a resource name against ARM guidelines
- get_arm_endpoints(), to return ARM endpoint and ARM credential scopes -
@vbfox @khalidabuhakmeh an RFC is already approved and partly implemented that accomplishes some of this. We’re hoping it’s stabilized before we GA our first #AzureSDK for Rust crates.
-
This may be enough for us to ditch our plans of using builders over ugly nested `..Default::default()` calls for nested client options in the #AzureSDK for rust. It wasn’t the only reason, but a significant one.
https://hachyderm.io/@ekuber/113369453953113824 -
We've been discussing internally and leaning toward transport-level mocking - fakes - like we do in our #AzureSDK for #golang: https://github.com/Azure/azure-sdk-for-go/blob/39d3aaa4b38dabada65b2683efc1d01e51e9bd30/sdk/resourcemanager/aad/armaad/fake/privateendpointconnections_server.go#L26
Basically, a struct which implements our `Policy` to be used as our transport in an already-pluggable pipeline and declares distinct `Arc<dyn Fn(..) -> impl Future<..>` fields that are mapped to endpoint calls.
Seems the most flexible and requires no change to the client API since we already support replacing the transport.
-
Would love feedback on mocking service clients for #AzureSDK for #rustlang: https://play.rust-lang.org/?version=stable&edition=2021&gist=12be3a45e8fccfa4f3ce06fd0744b6e1
Our current design requires pulling a trait into scope, and while rust-analyzer or other LSPs makes that easy not everything uses them: https://azure.github.io/azure-sdk/rust_introduction.html#rust-client-mocking
A colleague came up with a better way I prototyped above to better demo our current public API. The only caveat seems no worse than what we have now and should affect few developers, we believe.
-
@ekis @[email protected] I often work with monorepos like the #AzureSDK for #Go. That's when git worktrees and sparse checkouts can help reduce checkout time and drive space exhaustion. Check out https://heaths.dev/tips/2022/06/18/reduce-fetch-and-checkout-times-in-git.html for some tips. I should probably update that to mention worktrees too, though that really just helps reduce cloning time and minimizes disk space.
One advantage is having different copies of dependencies in different states, though I wonder how often that's a problem.
-
Great article with basic concepts to use Azure SDK 👉 https://devblogs.microsoft.com/azure-sdk/understanding-the-azure-core-library-for-net/ Since Azure SDK follow the same guidelines, using them is much easier and nicer. Unfortunately, some SDK (Cosmos, Azure IoT) still go their own way, but globally the dev experience has improved.
Yet, I still sometimes come across code that wraps Azure SDK. People, please stop that, it's useless and it prevents other developers to learn how to correctly use Azure SDK.
-
The #AzureDeveloperCLI `azd` has been available for a short while as a #devcontainer feature, which I recently used in https://github.com/heaths/azcrypto: https://github.com/heaths/azcrypto/pull/63/files#diff-24ad71c8613ddcf6fd23818cb3bb477a1fb6d83af4550b0bad43099813088686R8
It will not only install `azd`, but the #Azure dev extension for #VSCode. It makes deploying resources and applications a breeze.
I use it in azcrypto in lieu of the resource provisioning scripts I originally wrote for all of #AzureSDK to deploy resources uniformly. This is a publicly available (near) equivalent.
-
https://devblogs.microsoft.com/azure-sdk/understanding-the-azure-core-library-for-net/
Azure Core for all our language SDKs plays a core part of our HTTP pipeline (and other protocols in some cases, like AMQP), serialization, and more. My colleague, Anne, does a great job explaining a lot of it here. #Azure #AzureSDK
-
Now that the #golang #AzureSDK for #KeyVault has released v1.0.0, I have updated to it and released v1 of https://pkg.go.dev/github.com/heaths/a[email protected] : a cryptography client for Key Vault and #ManagedHSM that not only makes it easier to call crypto operations but tries to first cache the public key and do public key operations locally to improve performance and help mitigate throttling.
We have this in our other languages' SDKs but doesn't fit our design goals for #golang, so I wrote it as a separate module.
-
@larryosterman to clarify for others interested in #Azure or #AzureSDK, we - including others from different departments at #Microsoft - have established guidelines for both service APIs (typically REST) as well as client libraries we write and generate. Our code generators follow those same guidelines.
#TypeSpec is designed to bridge those concepts. With the same expressive grammar, service teams have more central control (with guard rails) over both service and client code.
