ci.environments.deleteDelete an environment with its rules and variables
DELETE /ci/api/repositories/{repoId}/environments/{name}IAM ci:DeleteEnvironmentChanges stateDestructive
Request syntax
DELETE /ci/api/repositories/{repoId}/environments/{name}Path parameters
repoIdRequiredstring
Constraints: uuid
nameRequiredstring
Constraints: 1-255 chars
Response
200 with no data; its variables and approvals go with it. 404 when the repository or the environment is not there. A workflow that names it again creates it again, without rules.
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 ci:DeleteEnvironment 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 ci environments delete repoId namecurl -X DELETE "https://console.platform.deutschecloud.app/ci/api/repositories/repoId/environments/name" \
-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_ci_environments_delete.