Post

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.

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.

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-....

Inspired by 1Password's CLI - which my family loves @1password.bsky.social - and to do some usability testing, I also developed crates.io/crates/akv-cli: a #rustlang CLI that installs as `akv` and is mostly call-compatible with `op` to fetch secrets without storing them in environment variables.

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?

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.