Hanzo
CLIIngress

Ingress

18 `hanzo` commands for Ingress, each calling one operation on api.hanzo.ai.

Package ingress is your front door: automatic TLS certificates and hostname routing to any backend, changed live.

18 commands · API reference →

CommandCallsWhat it does
hanzo ingress middlewares get <id>GET /v1/ingress/middlewares/{id}Returns one of the caller org's edge transforms by id.
hanzo ingress middlewares set <id>PUT /v1/ingress/middlewares/{id}Creates or replaces one edge transform and hot-applies it.
hanzo ingress middlewares rm <id>DELETE /v1/ingress/middlewares/{id}Removes one of the caller org's edge transforms and hot-applies the change.
hanzo ingress middlewares listGET /v1/ingress/middlewaresReturns every edge transform the caller's org has configured, ordered by id.
hanzo ingress middlewares createPOST /v1/ingress/middlewaresCreates or replaces one edge transform and hot-applies it.
hanzo ingress routes get <id>GET /v1/ingress/routes/{id}Returns one of the caller org's routing rules by id.
hanzo ingress routes set <id>PUT /v1/ingress/routes/{id}Creates or replaces one routing rule and hot-applies the new table — there is no config file and no restart.
hanzo ingress routes rm <id>DELETE /v1/ingress/routes/{id}Removes one of the caller org's routing rules and hot-applies the shrunken table, freeing its host for another claim.
hanzo ingress routes listGET /v1/ingress/routesReturns every routing rule the caller's org has configured, ordered by id.
hanzo ingress routes createPOST /v1/ingress/routesCreates or replaces one routing rule and hot-applies the new table — there is no config file and no restart.
hanzo ingress services get <id>GET /v1/ingress/services/{id}Returns one of the caller org's backend pools by id.
hanzo ingress services set <id>PUT /v1/ingress/services/{id}Creates or replaces one backend pool and hot-applies it.
hanzo ingress services rm <id>DELETE /v1/ingress/services/{id}Removes one of the caller org's backend pools and hot-applies the change.
hanzo ingress services listGET /v1/ingress/servicesReturns every backend pool the caller's org has configured, ordered by id.
hanzo ingress services createPOST /v1/ingress/servicesCreates or replaces one backend pool and hot-applies it.
hanzo ingress statusGET /v1/ingress/statusStatus reports the ingress edge's live posture: the role this instance runs in (app or edge), whether its listeners are…
hanzo ingress tls getGET /v1/ingress/tlsGetTLS returns the caller org's ACME intent together with the edge-wide TLS facts it lands in: which role this instance…
hanzo ingress tls replacePUT /v1/ingress/tlsPutTLS replaces the caller org's ACME intent and hot-applies what can be hot-applied.

How is this guide?