lb.rules.removeRemove a rule
DELETE /lb/api/load-balancers/{id}/rules/{ruleId}IAM lb:RemoveRuleChanges stateDestructive
Request syntax
DELETE /lb/api/load-balancers/{id}/rules/{ruleId}Path parameters
idRequiredstring
Constraints: uuid
ruleIdRequiredstring
Constraints: uuid
Response
200 with { id } of the removed rule; live on the fleet within seconds. 404 when the rule is not on this load balancer.
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 lb:RemoveRule 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 lb rules remove id ruleIdcurl -X DELETE "https://console.platform-development.deutschecloud.app/lb/api/load-balancers/id/rules/ruleId" \
-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_lb_rules_remove.