Execute the teardown plan the operator confirmed.
curl --request POST \ --url https://stratum.example.com/v1/admin/services/db/teardown \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "planId": "example" }'Records the teardown (tenant routes answer 503 from here on), issues
each listed resource’s own delete as the operator, and returns 202. A
reconciler finishes it and switches the service off once none is left;
follow it with GET. Audited Critical
(platform.service.teardown.started / .completed). A teardown that
cannot finish is stopped with POST…/teardown/cancel.
Refusals:
409 PLAN_STALE: the resources changed since the plan was shown. The body carries the freshplan; show it and confirm again.409 TEARDOWN_BLOCKED: an item has a blocker. The body carries theplan.409 TEARDOWN_RUNNING: one is already running.409 TEARDOWN_NOT_SUPPORTED: the service has no teardown.
Cedar action: platform:ManageServices.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”A registered service key. images and lb are always-on services with no
registry row, so they are not addressable here.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Example generated
{ "planId": "example"}Responses
Section titled “Responses”Started; the plan as executed.
What a service teardown would delete, grouped by project. The console shows it in the standard confirm modal; executing requires this planId, and a plan whose resources changed since is refused (PLAN_STALE).
object
A hash of the listed resources, not a stored object.
object
One live tenant resource a teardown deletes.
object
Db-instance, backup-plan or client-vpn-endpoint.
A database instance keeps a final snapshot, which is not deleted.
The final snapshot’s name, for final-snapshot-then-delete.
Why a teardown cannot delete it (deletion protection, a blue/green member). Clear it through the resource’s own API; the plan cannot be executed while any item is blocked.
Where the resource is now, in progress (e.g. “deleting”).
At least one item has a blocker; executing is refused.
Example
{ "projects": [ { "items": [ { "action": "delete" } ] } ]}Bad request.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Authenticated but not authorized.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Resource not found.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Refused. PLAN_STALE and TEARDOWN_BLOCKED answer with the plan
(ServiceTeardownConflict); TEARDOWN_RUNNING and
TEARDOWN_NOT_SUPPORTED with a plain problem.
A refused teardown execute. PLAN_STALE carries the fresh plan to show
and confirm again; TEARDOWN_BLOCKED carries the plan with each item’s
blocker.
object
What a service teardown would delete, grouped by project. The console shows it in the standard confirm modal; executing requires this planId, and a plan whose resources changed since is refused (PLAN_STALE).
object
A hash of the listed resources, not a stored object.
object
One live tenant resource a teardown deletes.
object
Db-instance, backup-plan or client-vpn-endpoint.
A database instance keeps a final snapshot, which is not deleted.
The final snapshot’s name, for final-snapshot-then-delete.
Why a teardown cannot delete it (deletion protection, a blue/green member). Clear it through the resource’s own API; the plan cannot be executed while any item is blocked.
Where the resource is now, in progress (e.g. “deleting”).
At least one item has a blocker; executing is refused.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "code": "PLAN_STALE", "plan": { "projects": [ { "items": [ { "action": "delete" } ] } ] }}