git.repositories.sync-push-mirrorPush to the push mirror now
POST /git/api/repositories/{repoId}/push-mirror/syncIAM git:ConfigurePushMirrorChanges stateDestructive
Request syntax
POST /git/api/repositories/{repoId}/push-mirror/syncPath parameters
repoIdRequiredstring
Constraints: uuid
Response
202 without `data`; the push is queued and its outcome lands in the repository's `pushMirror`. 409 without a push mirror.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
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 git:ConfigurePushMirror 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 git repositories sync-push-mirror repoIdcurl -X POST "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/push-mirror/sync" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_repositories_sync-push-mirror.