corestack_ deployments_ carryover_ accept
Accept the carried-over pipeline.
When to use it
Decide the carried-over lines waiting for review on one binding: accept, remove, or edit with one new line of text, each by the source stage and index corestack_deployments_carryover_get gives, with the binding's revision from it. Once no line is left in review the binding deploys again. Send lines: [] to accept a translation with nothing in review. An edit with text the stage does not run now also needs exec.
The same action in the public REST API, with the same checks, refusals and scope: POST /.
Ask for it
Using the Corefinity MCP server, call corestack_deployments_carryover_accept with site_id 4211, binding_id 812, lines [{"stage":"build","index":3,"action":"remove"}], revision r-8f2c. (Accept the carried-over pipeline.) Tell me what it returned.Inputs
At least 1.
Up to 600 items.
Fields of each item
acceptremoveeditAt least 0.
builddatabasepost_deployWith edit: the new line. Up to 4,096 characters.
The binding's revision from corestack_deployments_carryover_get; leave it out while that is null (a binding still classic).
At least 1.
Example call
{
"name": "corestack_deployments_carryover_accept",
"arguments": {
"site_id": 4211,
"binding_id": 812,
"lines": [
{
"stage": "build",
"index": 3,
"action": "remove"
}
],
"revision": "r-8f2c"
}
}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 translation or the pipeline changed since you read it; read it again and decide again. |
not_available | Nothing was carried into this binding. |
variable_invalid | A credential the carry moves into a variable cannot be stored; contact support. |
invalid_arguments | On lines.<n> with "This line still runs n98-magerun, which CoreStack does not have…": you accepted a line that still calls n98 (or magerun2, n98-magerun2) as it is, or edited a line into one that does. A line that only names it as a word (an echo, a here-string) counts too: reword it. CoreStack has no n98-magerun, so the deployment would fail on it. Edit the line to run its Magento commands as php bin/magento instead (php bin/magento cache:flush for n98 cache:flush), or remove it. The line's reason in corestack_deployments_carryover_get says the same. |
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. |
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. |