corestack_ varnish_ vcl_ revision_ get
Show one Varnish VCL revision.
When to use it
Read one custom Varnish VCL revision of a Magento 2 row by its number: the three hooks' text, its status, the reason a rejected or rolled-back revision carries and its diagnostics, with a line diff against the VCL now (the default) or against another revision.
Ask for it
Using the Corefinity MCP server, call corestack_varnish_vcl_revision_get with site_id 4211, number 3. (Show one Varnish VCL revision.) Tell me what it returned.Inputs
againststring
current, or another revision's number (such as "3", or "0" for the original) to diff against. Defaults to current. Up to 12 characters.
numberintegerRequired
The revision number from corestack_varnish_vcl_history_list. Revision 0 is the platform's original: the empty hooks every site starts with.
site_idintegerRequired
The row, a Magento 2 site or one of its environments. At least 1.
Example call
{
"name": "corestack_varnish_vcl_revision_get",
"arguments": {
"site_id": 4211,
"number": 3
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | The row has no revision with that number (or the row is not yours). |
varnish_not_offered | The row is not a Magento 2 site. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
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. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?