corestack_ ssh_ change_ get
Show an SSH key change.
When to use it
Follow an SSH key change: how many of the environments it reaches have applied it, how many wait for their switch-over, and which failed and why. The status tool of the ssh_change tasks.
The answer is state (applying, applied or failed), applied of total, waiting (environments that take the change at their switch-over or platform update), not_on_new_system and failed[] (environment ids and reasons). total counts only the environments on the new system or joining it: an environment that is not on the new system yet, and has not applied the change, is counted in not_on_new_system and never as applying, waiting or failed (one that applied it before it left counts as applied). So a change whose other environments have all applied it is applied, and one whose environments are all outside is applied with total 0. Its task completes then too. A note says when not_on_new_system is above 0; do not say the change failed or is waiting for those environments.
A managed CoreStack Enterprise target whose environment has been deleted remains
unconfirmed until its SSH target cleanup is verified. Its removal reports failed
with “SSH removal requires staff verification.” Deleting a panel row never proves
revocation. Staff reconcile the pinned target; a reused or unreadable target keeps
an owned critical residual. The same rule applies to the Control Panel and REST
GET /api/ssh/changes/{change}. No credentials or key material appear in the reason. Older deliveries can lack
complete grant attribution after an agency link changes. Such a removal remains
recorded and unconfirmed; polling refuses ssh_environment_unmanaged with “SSH
removal requires staff verification of an earlier delivery.” No other tenant's
ids or counts are returned. Staff verification of the retired target resolves it.
Ask for it
Using the Corefinity MCP server, call corestack_ssh_change_get with change_id 991201. (Show an SSH key change.) Tell me what it returned.Inputs
At least 1.
Example call
{
"name": "corestack_ssh_change_get",
"arguments": {
"change_id": 991201
}
}If it is refused
| Reason | What to do |
|---|---|
switched_off | SSH keys are not switched on for this object yet. |
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. |