Microsoft Azure SDK for Rust
Initial release of the Azure storage queue crate, as per gentle request of #319.
This is likely the last release of this repository before migrating into the Microsoft Open source one.
This is a maintenance release, it only fixes #317.
This minor release add a feature flag called azurite_workaround.
This relaxes the requirements of the Azure Storage Blob crate to accept malformed responses (without a valid creation date). This should allow the crate to work with Azurite.
The default features are unchanged.
This release includes the great Damien Pontifex's PR in the title (#309). This will streamline the development experience.
| Crate | Fix | PR | Backwards-compatible | Credit |
|---|---|---|---|---|
| Azure AAD | AAD credential providers and 'default' pattern | #309 | :green_circle: | Damien Pontifex |
| Crate | Fix | PR | Backwards-compatible | Credit |
|---|---|---|---|---|
| Azure Storage Blob | Swapped crc&md5 with consistency in put_block_blob_response | https://github.com/MindFlavor/AzureSDKForRust/pull/312 | :yellow_circle: (minimal impact) | Ayush Goyal |
This minor fix should make using Arc<dyn Client> as simple to use as Box<dyn Client>. Special thanks to Clemens Winter for all the help he's giving in isolating and solving these issues! :1st_place_medal:
Since this change impacts the core crate, the other crates have been bumped as well (even if there are no changes).
This is a first implementation of the refresh token support. It has been tested successfully with the device code flow but it should support other flows as well.
This also shuffles the structs/types around a bit, in preparation for a more cohesive crate.
Fixes #290.
This release also migrates the aforementioned crate from the failure crate to the thiserror one.
For a commented, working example on how to use the device code flow authentication, please see examples/device_code_flow.rs.
authorize_interactive with authorize_code_flow (see auth-code-flow).authorize_non_interactive with authorize_client_credentials_flow (see client-creds-grant-flow).