dcloud deploy kill-switches applyPull a kill switch on an app
route_offline: target is one of the app’s hostnames, or a path prefix such as /admin on every hostname of a machine-hosted app; it answers 503 (a pooled app’s host answers 404 for a hostname taken offline). private_only: only private-network sources (RFC 1918, the app’s VPC) are served, public ones get 403 — HTTP-level, TLS still completes; behind a load balancer the balancer itself is refused; not for pooled apps (409). scale_to_zero: every container stops; machines stay on and are billed; a deployment started meanwhile also stays at zero. Effective on the machines’ next poll, within seconds. A switch survives deploys, app updates and Terraform applies, and is never released by the platform. Pulling an active switch again returns it (200).
Synopsis
dcloud deploy kill-switches apply id --kind kind --reason reason [flags]Arguments
<id>Requiredstring
Also accepted as
--id. Constraints: uuid
Flags
--kindRequiredenum
route_offline, private_only or scale_to_zero
One of:
route_offline,private_only,scale_to_zero--targetOptionalstring
route_offline only: one of the app’s hostnames, or a path prefix such as /admin
--reasonRequiredstring
Why, for the record (3–500 characters)
Constraints: 3-500 chars
--finding-idOptionalstring
The Security Posture finding it answers, if any
Example
dcloud deploy kill-switches apply id --kind route_offline --reason exampleGenerated from the API description, the same one the API checks requests against and the CLI is built from.