Hanzo
OpenapiDeploy

The console's rollback control — today it requests a reconcile, nothing more

Performs exactly what the sync action performs: it stamps the sync-requested timestamp onto the application's App CR and answers the application…

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

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

Performs exactly what the sync action performs: it stamps the sync-requested timestamp onto the application's App CR and answers the application re-projected. It does NOT select, pin or revert to a prior image tag, and that is the one thing to know before wiring anything to it — the name is the console's, the behaviour is the sync. Pinning a previous release rides the release seam, which this address does not call yet.

SuperAdmin-only and fail-closed, reading no request body, with an unknown application name a 404 and no cluster client a 503 — the same gate and the same failures as the sync it shares a handler with.

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 rollback <name>

Deploy API · All Hanzo APIs · Interactive reference

How is this guide?

On this page