ecr.registry-aliases.putSet the registry aliases (replaces the list)
An alias { from: "ghcr.io/acme", to: "acme" } makes ghcr.io/acme/… in a workflow file this registry's acme/… and `docker login ghcr.io` this registry, in the job a runner receives. A job logs in with its GITHUB_TOKEN (packages: read pulls, write pushes and creates repositories inside the namespace). References in repository scripts, composite actions and Dockerfiles are not rewritten.
Request syntax
PUT /ecr/api/registry-aliases
{
"aliases": "array of json"
}Request body
aliasesRequiredarray of json
The whole list, at most 20: [{ "from": "ghcr.io/acme", "to": "acme" }]. from is host/owner; to is a namespace in this registry. Each from once; [] removes every alias
Response
200 with { aliases } as saved (from and to trimmed and lowercased). 400 when a from appears twice.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow ecr:PutRegistryAliases on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud ecr registry-aliases put --aliases '["example"]'curl -X PUT "https://console.platform-development.deutschecloud.app/ecr/api/registry-aliases" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"aliases":["example"]}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ecr_registry-aliases_put.