corestack_ deployments_ pipeline_ template_ reset
Reset a pipeline to its template.
When to use it
Make stages of one environment's pipeline follow its deployment template again: the template's content is written now and used from the next deployment, and the previous content stays in the version history. With version (a version_ref from corestack_) the stages hold that earlier version here instead, and later template saves do not reach them until a reset without version. Send the pipeline revision you read; production needs confirm_production: true. A command the pipeline does not run now also needs exec.
The same action in the public REST API, with the same checks, refusals and scope: POST /, the binding being the environment's first.
Ask for it
Using the Corefinity MCP server, call corestack_deployments_pipeline_template_reset with site_id 4211, stages ["post_deploy"], revision r-8f2c. (Reset a pipeline to its template.) Tell me what it returned.Inputs
The pipeline revision you read.
At least 1.
The stages, or ["all"]. Up to 4 items.
builddatabasepost_deploysettingsallA version_ref from corestack_: hold that version here instead.
Your assistant fills in a confirmation only after you agree.
Example call
{
"name": "corestack_deployments_pipeline_template_reset",
"arguments": {
"site_id": 4211,
"stages": [
"post_deploy"
],
"revision": "r-8f2c",
"confirm_production": true
}
}If it is refused
| Reason | What to do |
|---|---|
forbidden | The person's role lacks the Edit Environment Deployment Pipeline permission. The message names it and says an owner of the company can grant it in Roles; details.permission is editEnvironmentDeploymentPipeline. Nothing is changed. |
stale | The pipeline changed since you read it; read it again and resend. |
confirm | This is a production environment; send confirm_production: true. |
version_unavailable | That version is not one you can choose here. |
pipeline_classic | Corefinity still runs this pipeline in its classic form. |
pipeline_locked | Corefinity has locked this pipeline. |
not_reached | This environment does not follow a template yet. |
node_too_old | The template's stage needs a newer Node.js than this environment runs (Shopware's shopware_storefront and shopware_administration presets need Node.js 20). |
preset_unavailable | The template's preset is not available here, such as shopware_cli on an environment whose PHP image has no shopware-cli, or Shopware's shopware_storefront and shopware_administration presets on an environment without the runtime update ("This environment needs the runtime update before it can build with the Shopware storefront and administration presets."; corestack_runtime_adopt). Where the template's shopware_auto builds with shopware-cli, shopware-cli builds the storefront and administration itself and the two presets are left out. |
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. |
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. |
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. |
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. |