Feature Description
The Vercel artifact backend has a well-known URL, but even at Vercel we often use the same HTTP protocol with a different backend endpoint (along with team ID and slug).
Problem and Solution
The API documentation page (https://vercel.com/docs/rest-api/artifacts/upload-a-cache-artifact) lists a number of other parameters, but endpoint URL and team id/slug are the most useful to configure when using opendal with the Vercel artifact backend.
The configuration would end up looking like:
access_token: set the access_token for Rest API
endpoint: set the API endpoint (default: https://api.vercel.com)
team_id: optional Vercel team ID, appended as teamId query parameter
team_slug: optional Vercel team slug, appended as slug query parameter
Additional Context
No response
Are you willing to contribute to the development of this feature?
Feature Description
The Vercel artifact backend has a well-known URL, but even at Vercel we often use the same HTTP protocol with a different backend endpoint (along with team ID and slug).
Problem and Solution
The API documentation page (https://vercel.com/docs/rest-api/artifacts/upload-a-cache-artifact) lists a number of other parameters, but endpoint URL and team id/slug are the most useful to configure when using opendal with the Vercel artifact backend.
The configuration would end up looking like:
access_token: set the access_token for Rest APIendpoint: set the API endpoint (default:https://api.vercel.com)team_id: optional Vercel team ID, appended asteamIdquery parameterteam_slug: optional Vercel team slug, appended asslugquery parameterAdditional Context
No response
Are you willing to contribute to the development of this feature?