deploy.registry-credentials.list

List the registry credentials of an app (never the password)

GET /deploy/api/apps/{id}/registry-credentialsIAM deploy:DescribeAppRead

Request syntax

GET /deploy/api/apps/{id}/registry-credentials

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with `data`: one entry per registry — id, appId, registryHost, username, passwordSecretId (the Secret holding the password, null if it was deleted), createdAt and updatedAt.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

  • [].​idAlways

    string

    Credential id
  • [].​appIdAlways

    string

    The app
  • [].​registryHostAlways

    string

    Registry host, e.g. ghcr.io
  • [].​usernameAlways

    string

    User name the machine signs in with
  • [].​passwordSecretIdAlways

    string, may be null

    The Secret holding the password; null if it was deleted
  • [].​createdAtAlways

    string

    When it was added
  • [].​updatedAtAlways

    string

    When it was last changed

Checked against the handlers: every route test validates their answers against this schema.

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 deploy:DescribeApp 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 deploy registry-credentials list id

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