vercel-artifacts

4 configuration options · available in Rust, Python, Node.js, Java

Quick start
use opendal::Operator;

let op = Operator::via_iter("vercel-artifacts", [
])?;

All configuration options (copy & trim)

Full reference
use opendal::Operator;

let op = Operator::via_iter("vercel-artifacts", [
    // The access token for Vercel.
    // ("access_token".to_string(), "...".to_string()),

    // The endpoint for the Vercel artifacts API.
    //
    // Defaults to `https://api.vercel.com`.
    // ("endpoint".to_string(), "...".to_string()),

    // The Vercel team ID. When set, the `teamId` query parameter
    // is appended to all API requests.
    // ("team_id".to_string(), "...".to_string()),

    // The Vercel team slug. When set, the `slug` query parameter
    // is appended to all API requests.
    // ("team_slug".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.

Configuration reference

General4

Key	Type	Required	Description
`access_token`	string	no	The access token for Vercel.
`endpoint`	string	no	The endpoint for the Vercel artifacts API. Defaults to `https://api.vercel.com`.
`team_id`	string	no	The Vercel team ID. When set, the `teamId` query parameter is appended to all API requests.
`team_slug`	string	no	The Vercel team slug. When set, the `slug` query parameter is appended to all API requests.