Upgrade Template
upgrade_templateUpgrade an installed release to a new version (omit it for the latest available) with its complete values. Identify the release by name only: the template and GVC are immutable and read from the installed release, so you do NOT pass them. values REPLACE the release's current values entirely (no merge): start from the values it runs with now, which the user reads in the Console and never pastes into the chat, not the template example. Verify with get_installed_template after.
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": {
"name": "<name>",
"values": "<values>"
},
"name": "upgrade_template"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| org | No | Organization slug. | |
| name | Yes | Release name — the unique, immutable identifier for this installed instance within the org. | |
| values | Yes | The complete values.yaml for the release going forward — it REPLACES the currently applied values entirely (there is no reuse-values merge). Preserve the release's CURRENT non-sensitive settings, not the template example, or customized settings fall back to defaults. The user can inspect current values privately in the Console; never fetch or paste credential-bearing values into chat. If current values require literal credentials, upgrade privately in the Console instead. | |
| version | No | Target version to upgrade to. Omit for the latest available version. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | The full result. Read this, not only the summary. | |
| details | No | ||
| summary | Yes | ||
| nextSteps | No |