Hanzo
CLIDeploy

Deploy

20 `hanzo` commands for Deploy, each calling one operation on api.hanzo.ai.

Package deploy is Hanzo CD: see what each app is running, sync it, and roll back a bad release.

20 commands · API reference →

CommandCallsWhat it does
hanzo deploy applications resource-tree <name>GET /v1/deploy/applications/{name}/resource-treeReturns one application's argocd ApplicationTree: the objects the operator reconciled from its App CR, reached by…
hanzo deploy applications revisions metadata <name> <revision>GET /v1/deploy/applications/{name}/revisions/{revision}/metadataReturns the argocd RevisionMetadata for one revision of one application — what the detail view shows beside a revision.
hanzo deploy applications rollback <name>POST /v1/deploy/applications/{name}/rollbackThe console's rollback control — today it requests a reconcile, nothing more
hanzo deploy applications sync <name>POST /v1/deploy/applications/{name}/syncAsk the operator to reconcile one application now
hanzo deploy applications syncwindows <name>GET /v1/deploy/applications/{name}/syncwindowsReturns one application's argocd ApplicationSyncWindowState — the answer to "is anything blocking a sync of this…
hanzo deploy applications get <name>GET /v1/deploy/applications/{name}Returns ONE projected argocd Application by name, with status.resources filled in from its reconciled resource tree —…
hanzo deploy applications listGET /v1/deploy/applicationsReturns the fleet as an argocd ApplicationList: one projected Application per operator App CR, carrying the image tag…
hanzo deploy callbackGET /v1/deploy/callbackFinish the sign-in round trip and mint the console session
hanzo deploy clustersGET /v1/deploy/clustersReturns the argocd ClusterList of the destinations the caller's applications reconcile into: one entry per distinct…
hanzo deploy gitopsGET /v1/deploy/gitopsLists every Hanzo CD Application in the cluster: the git source each one polls, the commit it last APPLIED, how its…
hanzo deploy healthGET /v1/deploy/healthWhether this control plane can actually reach the cluster it deploys to
hanzo deploy loginGET /v1/deploy/loginStart the sign-in round trip for this console
hanzo deploy logoutPOST /v1/deploy/logoutEnd the console session on this host
hanzo deploy projectsGET /v1/deploy/projectsReturns the argocd AppProjectList this console groups and filters applications by.
hanzo deploy reconcilePOST /v1/deploy/reconcileRender the configured git source and apply it to the cluster, once
hanzo deploy session userinfoGET /v1/deploy/session/userinfoAnswers "is this browser signed in, and if not where does it sign in?" — the dashboard SPA's bootstrap question, and…
hanzo deploy settingsGET /v1/deploy/settingsReturns the argocd AuthSettings object the dashboard SPA awaits before its first render.
hanzo deploy stream applications resource-tree <name>GET /v1/deploy/stream/applications/{name}/resource-treeLive resource tree for one application, as Server-Sent Events
hanzo deploy stream applications listGET /v1/deploy/stream/applicationsLive application fleet updates as Server-Sent Events
hanzo deploy versionGET /v1/deploy/versionReturns the argocd VersionMessage the dashboard SPA reads at bootstrap.

How is this guide?