update_artifact
Update an existing deployed artifact with new source files. vibeD stores the new source tarball and re-injects it into the app's warm sandbox — there is no per-deploy container build. A new version snapshot is created automatically.
Input Schema
| Parameter | Type | Required | Description |
|---|---|---|---|
artifact_id | string | Yes | ID of the artifact to update |
files | object | Yes | Updated file map (full replacement of source files) |
env_vars | object | No | Updated environment variables |
secret_refs | object | No | Updated secret references in format secret-name:key |
Example
{
"artifact_id": "a1b2c3d4",
"files": {
"index.html": "<!DOCTYPE html><html><body>Updated!</body></html>",
"style.css": "body { background: #000; color: #fff; }"
},
"env_vars": {
"NODE_ENV": "production"
}
}
Response
{
"artifact_id": "a1b2c3d4",
"name": "my-portfolio",
"url": "http://my-portfolio.default.localhost:31080",
"status": "running"
}
What Happens
- Validates the app exists and the caller owns it
- Stores the new source tarball (replaces the previous source)
- Re-injects the new source into the app's sandbox — no rebuild
note
Redeploy (POST /v1/apps/{id}/redeploy) is not yet fully wired. The supported update path is to deploy again under the same name.