xCloud
delete_environment
Delete an application's development environment and everything running or stored in it: its container, database, realm, credentials, files, and logs. Its version rows are withdrawn from `list_versions`. The call keeps the application, its production environment, its areas, and its declarations; production is deleted only with its application. Afterwards the application has one environment, so a deploy goes to production. On one environment the call is admitted where development's records stand: a database setup, whole or stopped partway, or a deletion of them that stopped. It then erases them, the secrets, files, and logs kept for local runs among them, and the next submit_manifest sets the database up again. Otherwise it is refused `environment_not_created`. Destructive: completes only after a person approves it in the browser.
Remote (network-hosted)
Other tools also called delete_environment?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"request_id": {
"type": "string",
"description": "Your request identity for this pending action: any string you choose. Repeating the call with the same request_id, from the same account, while the earlier pending action is still live — requested, approved, or executing — answers that pending action again and creates no second one. Once it has completed, failed, been declined, or expired, the same request_id starts a new one. Omitted, every call creates a new pending action."
},
"application": {
"type": "string",
"description": "The application id, from `list_applications`."
},
"environment": {
"type": "string",
"pattern": "^(development|production)$",
"description": "`development` alone; `production` is refused `invalid_request`, because production is deleted only with its application through `delete_application`. On an application with one environment the call is refused `environment_not_created`; after the deletion the application has one environment, and a deploy goes to production."
}
}
}