6 configuration options · available in Rust, Python, Node.js, Java
use opendal::Operator;
let op = Operator::via_iter("azfile", [
("share_name".to_string(), "...".to_string()),
])?;
use opendal::Operator;
let op = Operator::via_iter("azfile", [
// The root path for azfile.
// ("root".to_string(), "...".to_string()),
// The endpoint for azfile.
// ("endpoint".to_string(), "...".to_string()),
// The share name for azfile.
("share_name".to_string(), "...".to_string()),
// The account name for azfile.
// ("account_name".to_string(), "...".to_string()),
// The account key for azfile.
// ("account_key".to_string(), "...".to_string()),
// The sas token for azfile.
// ("sas_token".to_string(), "...".to_string()),
])?;
Every option is passed as a string key; OpenDAL parses it into the right type. Some services may require building the binding with the matching services-* feature enabled.
| Key | Type | Required | Description |
|---|---|---|---|
root | string | no | The root path for azfile. |
endpoint | string | no | The endpoint for azfile. |
share_name | string | yes | The share name for azfile. |
account_name | string | no | The account name for azfile. |
account_key | string | no | The account key for azfile. |
sas_token | string | no | The sas token for azfile. |