corestack_ enterprise_ deployment_ rollback
Roll back to a CoreStack Enterprise deployment.
When to use it
Put an earlier successful CoreStack Enterprise deployment live again: the deployments list's Rollback. Its commit is
deployed once more, built from the pipeline as it is now. A release that was deployed by image digest is put back
from the images it recorded instead, without a new build. Use corestack_ to find it: a
succeeded deployment with a git_commit that is not is_current.
A task follows the deployment to its end. The public API's
POST / answers the same.
On pipeline v1 the rollback never reuses the old release folder on the server: the commit is built and deployed into a
new release. So it still works once that folder has been removed by old-release pruning, which, where it is switched
on, keeps an environment's newest releases (3 by default, the live one included) and removes older folders after each
successful deployment. What pruning does take away is pointing htdocs back at an old releases/ folder by hand over
SSH: for an older release, roll back here instead.
Ask for it
Using the Corefinity MCP server, call corestack_enterprise_deployment_rollback with enterprise_env_id 1530, deployment_id 185101. (Roll back to a CoreStack Enterprise deployment.) Tell me what it returned.Inputs
The earlier successful deployment to go back to At least 1.
A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools. At least 1.
Example call
{
"name": "corestack_enterprise_deployment_rollback",
"arguments": {
"enterprise_env_id": 1530,
"deployment_id": 185101
}
}If it is refused
| Reason | What to do |
|---|---|
stale | That deployment cannot be rolled back to: it did not succeed, has no commit, is already the live release, or (pipeline v2) its image is no longer kept, or (deployed by image digest) the images it ran are no longer all recorded; or it moved on since it was read. |
artifact_pruned | That deployment's archive was removed after 30 days, so it can't be rolled back to. Deploy again from the commit (corestack_). Archives are kept for 30 days, and always for an environment's 10 most recent deployments and its newest successful one. |
busy | The same rollback is still being applied. forbidden: the person's role lacks the Rollback Deployments permission. The message names it and says an owner of the company can grant it in Roles; details.permission is rollbackDeployments. |
invalid_arguments | A CoreStack or CoreCluster environment; use corestack_deployment_rollback by site_id. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
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. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
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. |