corestack_ company_ deployment_ connection_ delete
Remove a deployment connection.
When to use it
Remove one of your company's deployment connections, for example an account that has left the company or a duplicate. Only the company's owners may remove a connection, and only while no environment deploys through it: move each environment that uses it to another connection first (its deployment settings in the Control Panel, or corestack_deployments_repository_set for a site). Nothing else is deleted: the environments keep their repository settings.
To repair a connection that needs re-authorising, do not remove it: reconnect it through reconnect_url from corestack_, which keeps every environment that uses it.
Removing cannot be undone. Ask the person first, then send confirm_connection set to the connection's id.
Ask for it
Using the Corefinity MCP server, call corestack_company_deployment_connection_delete with connection_id 42. (Remove a deployment connection.) Tell me what it returned.Inputs
The same id again, sent only after the person agreed. Without it, or with another id, nothing is removed and the refusal says what to send. At least 1.
The connection to remove, from corestack_. At least 1.
Your assistant fills in a confirmation only after you agree.
Example call
{
"name": "corestack_company_deployment_connection_delete",
"arguments": {
"connection_id": 42,
"confirm_connection": 42
}
}If it is refused
| Reason | What to do |
|---|---|
forbidden | You are not one of the company's owners; ask an owner or Corefinity support. |
conflict | Environments still deploy through the connection; details.environments names them and details.other_environments counts the ones not named to you. Nothing was removed. |
confirm_mismatch | confirm_connection is missing or is not the connection's id. Nothing was removed. |
tenant_mismatch | No such connection in your company. |
pin_refused | A token limited to some sites cannot change company-wide settings. |
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. |
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. |