iam.roles.trust-ci

Let this platform's CI assume the role wherever it trusts GitHub Actions, for the repositories imported or mirrored here

POST /iam/api/roles/{id}/trust-ciIAM iam:UpdateAssumeRolePolicyChanges stateDestructive

Each Allow statement whose principal is the GitHub Actions identity provider gets a twin for this CI (its provider is added when missing, which needs iam:CreateOpenIdConnectProvider): the same conditions, with repo:<owner>/<repo> mapped to the repository here. GitHub keeps working. Statements that pin only by numeric ids are skipped and listed.

Request syntax

POST /iam/api/roles/{id}/trust-ci

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with { id, added, skipped, trustPolicy }: how many twin statements were added (0 when they all exist already), why a statement trusting GitHub got none (one line each), and the trust policy as stored (JSON text). 404 for an unknown role; 409 when the role has no trust policy or the organization has no GitHub Actions identity provider; 400 when the result does not validate.

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 iam:UpdateAssumeRolePolicy 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 iam roles trust-ci id

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