Revise application setup
revise_application_setupNegotiate the setup Ankra proposed for an Application by changing the defaults on its deploy option contract, and commit the rewritten .ankra/ankra.yaml to the Application's setup pull-request branch. Use this for requests like '8Gi is too much, this is a demo' (database_storage), 'make it highly available' (database_instances, replicas) or 'expose it at shop.example.com' (ingress_enabled, ingress_host). Call get_application_setup_proposal first: only options the contract already declares can be changed, and every value must satisfy that option's declared type. The revision is all-or-nothing - if any requested change is refused, the proposal is left exactly as it was and the answer names each refusal and why, so never re-offer the unchanged plan as though the request had been honoured. The database ENGINE is not an option: Ankra generates PostgreSQL through the CloudNativePG operator, and swapping it means regenerating the setup rather than revising its contract. This never deploys anything - it writes one commit on the setup branch and updates the stored contract; the user still has to deploy.
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": {
"application_id": "<application_id>",
"options": "<options>"
},
"name": "revise_application_setup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| options | Yes | The deploy options to change, as a name-to-new-default object (for example {"database_storage": "1Gi", "replicas": "3"}). Every value is a string because the deploy contract stores defaults as text. Options not named here keep their current defaults. | |
| application_id | Yes | The Application's id. |