corestack_ environment_ starts_ with_ get
What a new environment starts with.
When to use it
Before corestack_environment_create: what a new staging environment of a site starts with. It tells you which firewall
addresses and presets the new environment inherits, whether SSH to it is closed to every other address from its first
minute, which SSH keys it gets, and that it is protected by HTTP authentication. Nothing is created or changed.
Ask for it
Using the Corefinity MCP server, call corestack_environment_starts_with_get with site_id 4211. (What a new environment starts with.) Tell me what it returned.Inputs
site_idintegerRequired
Any row of the site: the site or one of its environments. A pinned token needs the same pins as corestack_environment_create: a pin on the whole site, or on its cluster. A pin on one of its environments is not enough. At least 1.
Example call
{
"name": "corestack_environment_starts_with_get",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | A site you cannot see, another company's site or one that does not exist (a purged site included), or environments are not available. |
managed_elsewhere | Another control panel manages the site. This comes before anything else about the site, as corestack_environment_create refuses it. |
deleted | The site is deleted (in its grace period), so no environment can be added to it. This is the same refusal corestack_environment_create gives: "This site is deleted. Restore it first." Restore it with corestack_site_restore_deleted first. |
provisioning | The site is still being created. This is the same refusal corestack_environment_create gives: "The site is still being created. Try again once it is ready." |
site_unadopted | Refused for the same reason and in the same words as corestack_environment_create. |
pin_refused | Your token is pinned, and not to the whole site or its cluster ("Adding an environment needs a pin on the whole site", as corestack_environment_create answers), or its pins do not cover the row you named. |
rate_limited | More than 60 reads a minute (one budget with the Control Panel and the API). |
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. |
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. |
What it answers
firewall(null while the firewall is not available for the site):inherited: the number of addresses the new environment starts with. These are the website's own entries and those of its company, the company's agencies and their users. Only addresses that apply now are counted (active and not expired), never another environment's own entries.items: one line per address:cidr,scope(both,sshorweb),layer(website,company,agencyoruser, the nearest level that holds it) andowner(type,id,name).presets: the preset subscriptions that reach every environment of the site:name,slug,ranges,layer,owner.stage: the stage of the platform scope the new environment joins (dark,prepare,enforce,pausedordeferred).closed_to_others: true when that scope enforces, so SSH is closed to every address not on the list.
ssh(null while SSH keys are not available for the site):keys: the number of SSH keys the new environment gets on its first delivery. These are the website's, its company's and the company's agencies' keys granted to every environment. A key limited to selected environments never reaches a new one.items: one line per key:name,layer,owner.state: null.
http_auth.enabled: always true.staff_platform_line: always false for a token.
The same task elsewhere
Was this helpful?