corestack_ deployments_ secret_ set
Set a registry secret.
When to use it
Add or change an npm or Composer registry secret the environment's builds install with, and optionally verify it with the registry. Without secret_id it creates one (kind, registry, token); with it, it changes what you send; secret_id with verify: true alone verifies a stored one. The token and username are write-only.
The same action in the public REST API, with the same checks, refusals and scope: POST / (a new secret) and PUT / (secret_id).
Ask for it
Using the Corefinity MCP server, call corestack_deployments_secret_set with site_id 4211, kind npm, label GitHub Packages, registry https://npm.pkg.github.com, scope @acme, token <the registry token>, verify true. (Set a registry secret.) Tell me what it returned.Inputs
auth_typestring
Composer.
http-basicbearergithub-oauthgitlab-tokenkindstring
On create.
npmcomposerlabelstring
registrystring
npm: an https:// URL; Composer: the host.
scopestring
npm: @scope. Up to 214 characters.
secret_idinteger
Update this secret. At least 1.
site_idintegerRequired
At least 1.
tokenstring
usernamestring
Composer http-basic.
verifyboolean
Ask the registry once.
Example call
{
"name": "corestack_deployments_secret_set",
"arguments": {
"site_id": 4211,
"kind": "npm",
"label": "GitHub Packages",
"registry": "https://npm.pkg.github.com",
"scope": "@acme",
"token": "<the registry token>",
"verify": true
}
}If it is refused
| Reason | What to do |
|---|---|
exists | A secret for that registry and scope is already saved; update it with its secret_id (in details.id). |
secret_invalid | The registry is not an HTTPS address on the public internet, or a field is not valid. |
upstream_unavailable | The registry could not be asked; try again later. |
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. |
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. |
The same task elsewhere
Was this helpful?