Prepare service retirement
prepare_service_retirementPrepare the retirement of a managed service (step one of ankra services delete). It records a review and returns everything the retirement removes - the stack, the namespace and any objects in it the service did not create, and every volume claim with the reclaim policy that decides its data - and what it keeps, with the digest confirm_service_retirement needs. Nothing is removed. acknowledge_data_loss must be true: retiring a service deletes its data, and no export is offered. Requires applications.deploy and stacks.delete.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"instance_id": "<instance_id>",
"expected_generation": "<expected_generation>",
"disconnect_consumer_ids": "<disconnect_consumer_ids>",
"acknowledge_data_loss": "<acknowledge_data_loss>"
},
"name": "prepare_service_retirement"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes | Service instance id (UUID) from list_service_instances. | |
| expected_generation | Yes | The instance generation the user reviewed, from get_service_instance. | |
| acknowledge_data_loss | Yes | Must be true: the user accepts that the service's data is deleted. | |
| disconnect_consumer_ids | Yes | Exactly the service's consumer binding ids (from get_service_instance), each once: the consumers that lose the service. Required; an empty list only when it has none. |