corestack_ varnish_ version_ change
Change a site's Varnish version.
When to use it
Change the Varnish version of a Magento 2 row while Varnish is on, up or down. Read corestack_varnish_get first: only versions in options[] with allowed: true are accepted, and recommended marks the version Adobe certifies for the installed Magento patch.
Before anything changes, the row's saved custom VCL is compiled against the target version; if it does not compile, nothing changes and the refusal lists each problem with its hook, line and column (fix the VCL with corestack_varnish_vcl_validate and corestack_varnish_vcl_update, passing varnish_version to validate against the target). Then one line of the site's settings changes, Varnish is rolled to the new version and the quick cache check runs. The cache starts empty, so the first requests for each page go to Magento.
The change takes about a minute and answers a task on its varnish_version operation (follow it with corestack_site_operation_get). With apply: window it waits for the row's next maintenance window and answers at once {operation: null,; the VCL is compiled again when the window opens. While Varnish is off, choose the version as you switch it on: corestack_varnish_set with version.
Ask for it
Using the Corefinity MCP server, call corestack_varnish_version_change with site_id 4211, to 8.0, acknowledge ["eol"]. (Change a site's Varnish version.) Tell me what it returned.Inputs
Required when the target's status is eol (end of life upstream; Corefinity keeps its image patched). Up to 1 items.
eolNow (the default), or in the row's next maintenance window. Defaults to now.
nowwindowtonightThe row, a Magento 2 site or one of its environments. At least 1.
The version, such as 8.0.
Example call
{
"name": "corestack_varnish_version_change",
"arguments": {
"site_id": 4211,
"to": "8.0",
"acknowledge": [
"eol"
]
}
}If it is refused
| Reason | What to do |
|---|---|
varnish_off | Varnish is switched off; switch it on with corestack_varnish_set and version. |
version_unsupported | The version is not allowed for this Magento; the message names the offered versions. |
vcl_incompatible | The saved VCL does not compile on the target; details.diagnostics lists {hook,. Nothing changed. |
not_available | This row's Varnish version cannot be managed from here; contact support. |
temporarily_unavailable | The compile check could not run just now; try again in a minute. |
change_in_progress | Or busy: another change on the row is unfinished; change_pending: a change waits for the window. |
invalid_arguments | An eol target without acknowledge: ["eol"], or a malformed input; fields names the argument. |
managed_elsewhere | Another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
internal_error | Something went wrong on our side. Quote the trace id to support. |