deploy.redeploy.applyRedeploy the live deployment’s source with the current configuration (no rebuild)
Request syntax
POST /deploy/api/apps/{id}/redeploy
{
"reason": "string"
}Path parameters
idRequiredstring
Constraints: uuid
Request body
reasonOptionalstring
Why, shown on the deployment; default "configuration applied by <user>"
Constraints: max 200 chars
Response
201 with `data`: { ok: true, deploymentId, generation, reusedDeploymentId } — the deployment started and the one whose source it reuses. 502 with the reason when it could not be started.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
okAlwaystrue
The deployment was starteddeploymentIdAlwaysstring
The deployment startedgenerationAlwaysnumber
Its generationreusedDeploymentIdAlwaysstring, may be null
The deployment whose source it runs again; null if none
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:DeployApp 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 redeploy apply idcurl -X POST "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/redeploy" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_deploy_redeploy_apply.