iam.roles.set-trust-policySet which federated workloads (e.g. GitHub Actions jobs) may assume a role
PUT /iam/api/roles/{id}/trust-policyIAM iam:UpdateAssumeRolePolicyChanges stateDestructive
Request syntax
PUT /iam/api/roles/{id}/trust-policy
{
"trustPolicy": "object"
}Path parameters
idRequiredstring
Constraints: uuid
Request body
trustPolicyRequiredobject
The trust policy, as a JSON object or JSON text: which identity providers, and which token claims, may assume the role; null removes it, so nobody can
Constraints: JSON
Response
200 with { id, trustPolicy }: the trust policy as stored (JSON text), or null when it was removed. An invalid document is answered 400 with every problem in errors.
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 set-trust-policy id --trust-policy '{}'curl -X PUT "https://console.platform-development.deutschecloud.app/iam/api/roles/id/trust-policy" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"trustPolicy":{}}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_roles_set-trust-policy.