deploy.rabbitmq.unbindRemove the binding (the broker and its user are unchanged)
DELETE /deploy/api/apps/{id}/rabbitmqIAM deploy:ManageBrokerBindingChanges stateDestructive
Request syntax
DELETE /deploy/api/apps/{id}/rabbitmqPath parameters
idRequiredstring
Constraints: uuid
Query parameters
envPrefixOptionalstring
Which binding to remove, by its envPrefix; default empty (the unprefixed one)
Constraints: max 32 chars, /^([A-Z][A-Z0-9_]*_)?$/
Response
200 with `data`: { id } of the removed binding. Its variables are gone from the next rollout.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The removed binding
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:ManageBrokerBinding 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 rabbitmq unbind idcurl -X DELETE "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/rabbitmq" \
-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_deploy_rabbitmq_unbind.