Hanzo
OpenapiDeploy

Ask the operator to reconcile one application now

Requests an immediate reconcile of one application by stamping a sync-requested timestamp onto its App CR, which the operator's watch observes, and…

POST /v1/deploy/applications/{name}/sync

Addresshttps://api.hanzo.ai/v1/deploy/applications/{name}/sync
MethodPOST
Operationpost_deploy_applications_by_name_sync
AuthAuthorization: Bearer $HANZO_API_KEY

Requests an immediate reconcile of one application by stamping a sync-requested timestamp onto its App CR, which the operator's watch observes, and answers the application re-projected. It ASKS, it does not apply: the operator performs the reconcile on its own clock, so a 200 means the request landed, not that the rollout finished — the returned row's running version still lags until it does. The CR is the desired source today, so this is a nudge; when git becomes the source the same address becomes apply-from-git.

SuperAdmin-only and fail-closed — a non-SuperAdmin is refused before any cluster object is read or patched, and the write surface stays admin-only while the tenant surface is read-only reflection. It reads no request body. An unknown application name is a 404; no cluster client configured is a 503.

Request

1 field.

FieldInTypeRequiredDescription
namepathstringyes

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo deploy applications sync <name>

Deploy API · All Hanzo APIs · Interactive reference

How is this guide?

On this page