Small project to add ACS Email support, it is working and can be tested with: cargo run --package azure_svc_communicationemail --example send_mail $ACS_ENDPOINT $ACS_KEY
This repository is for the development of the unofficial Azure SDK for Rust.
All Azure SDK for Rust crates are published on crates.io.
These SDK crates are available:
- azure_core
- azure_identity
- azure_data_cosmos
- azure_data_tables
- azure_iot_hub
- azure_security_keyvault
- azure_storage_blobs
- azure_storage_datalake
- azure_storage_queues
Azure service crates generated from Azure REST API Specifications are available in services.
๐จ WARNING ๐จ: This project is under active development. Be aware that large breaking changes will happen before 1.0 is reached.
This project is the successor to the azure_sdk*
crates from MindFlavor/AzureSDKForRust. The crates have been renamed, so those older crates should be considered fully deprecated. See history for more details.
Each supported Azure service is its own separate crate.
Building each crate should be as straight forward as cargo build
, but check each crate's README for more specific information.
This library comes with a testing framework that executes against prerecorded sessions to quickly validate code changes without incurring in Azure costs. You can read more about it in the Mock testing framework's README.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.