Struct AzureBlobStorage 

pub struct AzureBlobStorage { /* private fields */ }

Available on crate features storage-azure or storage-gcs or storage-local or storage-s3 only.

Azure Blob Storage object storage.

Signs every request with the Shared Key HMAC-SHA256 scheme using the outbound HTTP client (crate::http_client::Client) — no Azure SDK dependency. Credentials come from config.account_key when non-empty; otherwise they’re auto-detected from Managed Identity (App Service/Container Apps identity endpoint, or VM/AKS IMDS as a last resort), cached, and refreshed shortly before expiry. See crate::storage::azure_credentials and crate::storage::azure_signature.

Implementations

impl AzureBlobStorage

pub fn new(config: AzureBlobConfig) -> AzureBlobStorage

pub fn from_env() -> Result<AzureBlobStorage, StorageError>

Shortcut for AzureBlobStorage::new(AzureBlobConfig::from_env()?).

Trait Implementations

impl Storage for AzureBlobStorage

fn put( &self, key: &str, data: &[u8], content_type: &str, ) -> Result<String, StorageError>

Store data under key, overwriting any existing object at that key. Returns the key that was stored (backends that normalize or namespace keys may return a different string than the one passed in).

fn get(&self, key: &str) -> Result<Vec<u8>, StorageError>

Retrieve the bytes stored under key.

fn delete(&self, key: &str) -> Result<(), StorageError>

Delete the object stored under key. Backends generally treat deleting a missing key as a no-op success, matching S3’s semantics.

fn url(&self, key: &str) -> String

A URL for retrieving key. For LocalStorage this is only meaningful if a base URL was configured (e.g. because the directory is also served as static files); for S3Storage it’s the object’s HTTPS URL. This performs no I/O and never fails.

fn put_stream( &self, key: &str, reader: &mut dyn Read, content_type: &str, ) -> Result<String, StorageError>

Store everything reader yields under key — for a body too large to hold in memory, e.g. a streamed upload (Request::body read as a stream, #31). LocalStorage writes as it reads and S3Storage uploads in parts (S3 multipart upload), so memory stays at one part; the default reads everything first and calls Storage::put.