corestack_ deployment_ trigger
Deploy.
When to use it
Deploy a row from its connected repository now — its branch, or a branch or commit you name. With several pipeline bindings on the environment, binding_id deploys another one than the repository's (corestack_deployments_pipeline_get lists them).
Check first with corestack_ and tell the person what it found: a deployment stops at linking shared files when the settings file its platform needs (such as .env or app/etc/env.php) is in neither the shared folder nor the live release, unless the repository includes it, which no check can see before the build; the check names each missing file and where to create it over SFTP or SSH. It only advises: a deployment is never refused for its answer, so start when the person says so, whatever it found.
The call answers a task to follow. When the deployment fails, the task answers work_failed with the deployment row in details, and the row's error is the line the Control Panel shows: for example, a release holding a file that matches known malicious code is stopped before anything is built or changed, and error names the file.
With the pre-switch check on (the binding's deploy options), the new release is asked for its home page and up to five listed paths before it goes live; any answer but 200, 301 or 302 stops the deployment before the switch, the live release keeps serving, and error names the page and its answer (for example / answered 500).
The first Git deployment of a converted or moved site takes the shared files and folders the live release still holds itself (its .env, its uploads, a Bedrock project's .env and web/app/uploads) into the site's shared folder in place: renamed and linked back, never copied, so the live site keeps them whatever happens. An empty shared folder or file is set aside for them, never removed. It stops before the switch, with error saying why, when a shared path holds different content in the live release and in the shared folder (the counts are named; nothing is merged), when the live release reaches it through a link, or when a Bedrock release cannot reach its database. Only a database connection error stops a Bedrock release there (unless the pre-switch check option is on, which stops on any failure): when its WordPress cannot be asked (no WP-CLI, too little memory) or answers anything else, for example because WordPress is not installed in a new database yet, the deployment carries on and the step's output says it was not checked.
Ask for it
Using the Corefinity MCP server, call corestack_deployment_trigger with site_id 4211, ref main. (Deploy.) Tell me what it returned.Inputs
Another pipeline binding of the same environment; the repository's when left out. At least 1.
A branch or a commit SHA; the connected branch when left out. Up to 255 characters.
At least 1.
Example call
{
"name": "corestack_deployment_trigger",
"arguments": {
"site_id": 4211,
"ref": "main"
}
}If it is refused
| Reason | What to do |
|---|---|
forbidden | The person's role lacks the Create Deployments permission. The message names it and says an owner of the company can grant it in Roles; details.permission is createDeployments. Nothing is changed. |
pipeline_untranslated | The pipeline carried over from CoreStack Enterprise is not translated yet; contact support. |
pipeline_review_pending | Pipeline lines carried over are waiting for review; accept them (corestack_deployments_carryover_accept) first. |
pipeline_switched_off | The deployment pipeline this binding needs is switched off; the person should contact Corefinity. |
tunnels_switched_off | The build needs tunnels, which are switched off right now; try again later. |
feature_off | Choosing a binding is not available yet; deploy without binding_id. |
runtime_not_adopted | The build needs tunnels, which need the row's adopted runtime; adopt it with corestack_runtime_adopt first. |
invalid_arguments | With detail_reason no_repository (message: "Connect a repository first"): the site has no repository connected, so there is nothing to deploy; connect one with corestack_deployments_repository_set first. Nothing is created. The reason is the one this refusal has always answered; detail_reason names it. |
needs_reauth | The repository's connection is gone, or no longer belongs to the site's company ("This repository connection no longer belongs to this site's company. Connect the repository again."); bind the repository again through one of the site's own connections (corestack_deployments_repository_set). Nothing is created. |
site_content_off | The row's repository holds site content and Corefinity has paused deploying it ("Deploying site content is paused by Corefinity. Nothing was changed."); try again later, or set the repository to whole_site with corestack_deployments_repository_set if it holds the whole site. Nothing is created. |
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. |