Deploy

DeployResource

Methods

create() ->
post/v5/agentex/deployments

Create a new deployment.

Submits a deployment request. The deployment will:

  1. Parse and merge configuration files
  2. Create a Kubernetes Job running helm install
  3. Wait for deployment completion
  4. Return results
Parameters
environment_config: str
manifest_file: str
build_id: Optional[str]

The build_id of the cloud build. Required if image_name and image_tag are not provided.

image_name: Optional[str]

Name of the image to deploy. Required if build_id is not provided.

image_tag: Optional[str]

Tag of the image to deploy. Required if build_id is not provided.

preview: Optional[]

When True, creates a preview deployment with a unique slug appended to the helm release name.

Returns
id: str
account_id: str
created_at:
(format: date-time)
created_by:

The identity that created the entity.

environment_config: str
manifest_file: str
namespace: str
status: str
build_id: Optional[str]
deploy_events: Optional[List[]]

Kubernetes events for this deployment.

helm_release_name: Optional[str]
object: Optional[Literal["agentex_cloud_deploy"]]
(default: "agentex_cloud_deploy")
Request example
200Example
retrieve() ->
get/v5/agentex/deployments/{deployment_id}

Get a deployment by its ID.

list() -> SyncCursorPage[]
get/v5/agentex/deployments

List all deployments with pagination and optional filters.

logs(, ) ->
get/v5/agentex/deployments/{deployment_id}/logs

Get structured log lines for a deployment with cursor-based pagination.

The CLI can poll this endpoint to stream logs incrementally:

  1. First call: no cursor
  2. Subsequent calls: cursor=next_cursor from the previous response
  3. Stop polling when the deployment reaches a terminal status

Domain types

class AgentexCloudDeploy: ...
class AgentexCloudDeployEvent: ...

Slim event representation for the API response.

class DeployLogsResponse: ...

Response containing structured deployment log lines with cursor-based pagination.

The CLI can poll this endpoint to stream logs incrementally:

  1. First call: no after_id
  2. Subsequent calls: after_id=next_cursor from previous response
  3. Stop polling when has_more is False and the deployment reaches a terminal status