corestack_ deployments_ pipeline_ get
Deployment pipeline.
When to use it
Read a deployment pipeline before changing it: its build, database and post-deploy stages (every line redacted, with its check verdict and badges), its settings, placement, the presets on offer, the environment's deployment options and the revision every change must send. Pass binding_id for another binding of the environment. With version_id (from corestack_) it reads that saved version instead, with what differs per stage and setting from compare_to: the current pipeline, or another version. Never a variable value or a secret.
A pipeline comes in one of two layouts, named by stage_model:
three_stage:stagesholds the build, database and post-deploy lines you can change, andclassicis null.- a classic pipeline (
stage_modelnull):stagesandsettingsare null and changes are refused withpipeline_classic.classiclists what it actually runs: each block in the order the deployment runs it (on a version 3 site firstbuild_server, the platform's build commands run as oneBuildingstep on the build server; thenbuild; on a version 2 Kubernetes environmentdatabase, betweenmaintenance_onandmaintenance_offwhen maintenance mode brackets it; thenpost_build), each line under the name its step has on the deployment page (Build command 2), withsourcecustomfor the environment's own lines,sharedfor the platform's shared pipeline it inherits, orplatformfor the build server block. Credentials are redacted; a comment line is listed with the line it precedes.runsis false when the pipeline is refused at deploy and runs nothing.
On a version 2 environment a classic pipeline's build lines run while the live site keeps serving visitors, against its database. Database changes that need maintenance mode belong in the database commands, with maintenance mode switched on (the database block between maintenance_on and maintenance_off). The shared Magento 2 pipeline switches maintenance mode on in its build for the setup:upgrade line alone.
A classic pipeline's answer includes:
{
"stage_model": null,
"stages": null,
"classic": {
"pipeline_version": 3,
"runs": true,
"sections": [
{"key": "build", "label": "Build command", "source": "shared", "lines": [
{"label": "Build command 1", "command": "composer install --no-interaction --no-dev --optimize-autoloader", "comments": []}
]},
{"key": "post_build", "label": "Post build command", "source": "custom", "lines": [
{"label": "Post build command 1", "command": "php artisan migrate --force", "comments": ["# schema first"]}
]}
]
}
}The same action in the public REST API, with the same checks, refusals and scope: GET / (binding_id), and with version_id GET / (compare_to).
Ask for it
Using the Corefinity MCP server, call corestack_deployments_pipeline_get with site_id 4211, version_id 381, compare_to current. (Deployment pipeline.) Tell me what it returned.Inputs
Default: the environment's default binding. At least 1.
With version_id: current (the default) or another version_id.
At least 1.
A version from corestack_: read it instead of the current pipeline. At least 1.
Example call
{
"name": "corestack_deployments_pipeline_get",
"arguments": {
"site_id": 4211,
"version_id": 381,
"compare_to": "current"
}
}If it is refused
| Reason | What to do |
|---|---|
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. |