errors.connections.revoke-previous-key

Revoke the rotated-out key now (its events are refused from then on)

POST /errors/api/projects/{id}/rotate-key/revoke-previousIAM errors:UpdateProjectChanges state

Request syntax

POST /errors/api/projects/{id}/rotate-key/revoke-previous

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with { revoked: true }, without waiting for the grace or the rebuilds. 409 when no rotation is in progress; 404 when the project does not exist.

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 errors:UpdateProject 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 errors connections revoke-previous-key id

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