ecr.pull-through-cache.update

Set or clear a rule's upstream login

PATCH /ecr/api/pull-through-cache-rules/{id}IAM ecr:UpdatePullThroughCacheRuleChanges state

Request syntax

PATCH /ecr/api/pull-through-cache-rules/{id}
{
  "username": "string",
  "passwordSecretId": "string"
}

Path parameters

  • idRequired

    string

    Constraints: uuid

Request body

  • usernameRequired

    string

    Upstream user name, 1–255 characters, or null to drop the login. Required, and null exactly when passwordSecretId is

    Constraints: 1-255 chars

    May be null.

  • passwordSecretIdRequired

    string

    Id of a Secret of this organization holding the password or token (granted to the registry consumer), or null to drop the login. Required, and null exactly when username is

    May be null.

Response

200 with the rule as it now is: id, prefix, upstreamRegistry, upstreamLabel (e.g. Docker Hub), username and passwordSecretId (null without a login), repositories (how many cache repositories it has filled), createdAt. 400 when passwordSecretId names no secret of the organization; 404 for an unknown rule.

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:UpdatePullThroughCacheRule 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 pull-through-cache update id --username example --password-secret-id example

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ecr_pull-through-cache_update.