Get service retirement
get_service_retirementRead one retirement of a managed service (the twin of ankra services retirements get): its reviewed plan, state and phase, its outcome once settled, and what became of each reviewed volume once the namespace was gone. A retirement whose outcome is retired released the name; its data_disposal says whether the service's data may remain (data_kept, unconfirmed) and kept_data names the volumes, the cluster, when Ankra last looked and the Ankra CLI commands to inspect or erase them. Never report such a service as plainly deleted, and say kept_data is what Ankra saw then, not now. Use it to follow confirm_service_retirement until it settles. Read-only.
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>",
"retirement_id": "<retirement_id>"
},
"name": "get_service_retirement"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes | Service instance id (UUID). | |
| retirement_id | Yes | Retirement id (UUID) from prepare_service_retirement or get_service_instance. |