Deploy multiple functions in one request
Changed onUpload multiple function source archives in one multipart request. Each archive should contain source files plus dependency manifests/lockfiles, not installed dependency directories. ZIP and tar.gz uploads are accepted and normalized to tar.gz before storage. The API enforces SOURCE_ARCHIVE_SIZE_LIMIT_MB for each uploaded and normalized source archive. The server records a shared deployment batch ID for the resulting function deployments. Each function deployment runs its own compile/publish workflow concurrently, and each publish build enforces LAMBDA_TARGET_CONTAINER_SIZE_LIMIT_MB for the final container image. One batch request can include up to 100 functions. Submit multiple batch requests for larger projects. If one function fails before its workflow starts, already-started function deployments are left running and the failed function is reported in the failed array. Failed new functions are deleted; failed updates are rolled back to their previous metadata/status where possible.
Request
- Base URL: https://api.volcano.dev
- URL: https://api.volcano.dev/projects/{id}/functions/batch
- Auth: one of:
- HTTP bearer
- HTTP bearer
Path parameters
Project ID
Response
Batch deployment accepted
Changes
- ●
removed the optional property
//from the response with the status - ●
removed the optional property
//from the response with the status - ○
the endpoint scheme security
ProjectAccessTokenwas added to the API - ○
added the non-success response with the status
- ○
added the non-success response with the status
- ○
response property
data/items/is_publicdeprecated - ○
response property
data/items/is_publicdeprecated - ○
added the required property
//to the response with the status - ○
added the required property
//to the response with the status
- ●
- ▲
added the new path request parameter
id - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ○
added the non-success response with the status
- ○
added the non-success response with the status
- ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status
- ▲