Post

Heath Stewart
@heaths.dev

I'm excited to announce the first beta of our official #AzureSDK for #rustlang crates! This initial release includes Key Vault Secrets and Keys, Event Hubs including AMQP support, our core crates, and Identity. Cosmos is following soon. We have more planned including some usability improvements.

Heath Stewart
@heaths.dev

This was a long time coming and we have released many unofficial crate versions with a lot of help from the community. We had to make some changes to align with our other languages' SDKs, but with @larryosterman.github.io, @analogrelay.net, and many others, this is our first *official* release.

1 repost3 likes

Heath Stewart
@heaths.dev

We'll be adding more Identity credentials, more client libraries, changing model deserialization - just a single `await?` - and more, but would love for people to use these and file feedback at github.com/Azure/azure-....

github.comGitHub - Azure/azure-sdk-for-rust: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of li...This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK. - Azure/azur...
erewok
@erewok.bsky.social

hey, this looks pretty cool! I type out a lot of related az-cli commands every week, although I tend to primarily use --vault-name arg. Would you be up for adding a vault-name arg (which populates the URL automatically or open to a PR allowing vault-name in lieu of url?

Heath Stewart
@heaths.dev

Sorry, no. `--vault-name` in the `az` CLI is actually a bit of a problem since it depends on what cloud you're *currently* in. However, you can avoid typing it all the time with a .env file for debug builds. I don't support them in release builds currently, but not against enabling that.