Skip to content

Commit f2b8aa7

Browse files
hittytPangjiping
authored andcommitted
docs(server): clarify manual cleanup is runtime-dependent
Kubernetes providers may reject null timeout when the workload provider does not support non-expiring sandboxes. Make this constraint explicit in the OpenAPI spec and schema description. Made-with: Cursor
1 parent 71b77f1 commit f2b8aa7

2 files changed

Lines changed: 5 additions & 1 deletion

File tree

server/src/api/schema.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -319,7 +319,9 @@ class CreateSandboxRequest(BaseModel):
319319
description=(
320320
"Sandbox timeout in seconds (minimum 60). "
321321
"The maximum is controlled by server.max_sandbox_timeout_seconds. "
322-
"When omitted or null, the sandbox will not auto-terminate and must be deleted explicitly."
322+
"When omitted or null, the sandbox will not auto-terminate and must be deleted explicitly. "
323+
"Note: manual cleanup support is runtime-dependent; Kubernetes providers may reject "
324+
"null timeout when the workload provider does not support non-expiring sandboxes."
323325
),
324326
)
325327
resource_limits: ResourceLimits = Field(

specs/sandbox-lifecycle.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -780,6 +780,8 @@ components:
780780
Sandbox timeout in seconds. The sandbox will automatically terminate after this duration.
781781
The maximum is controlled by the server configuration (`server.max_sandbox_timeout_seconds`).
782782
Omit or set null to disable automatic expiration and require explicit cleanup.
783+
Note: manual cleanup support is runtime-dependent; Kubernetes providers may reject
784+
null timeout when the underlying workload provider does not support non-expiring sandboxes.
783785
784786
resourceLimits:
785787
$ref: '#/components/schemas/ResourceLimits'

0 commit comments

Comments
 (0)