delete-geographic-access-custom-region
dci delete-geographic-access-custom-region
Deletes a custom region owned by the authenticated tenant. Assigned regions cannot be deleted. Requires the UsersManager permission.
Assigned regions cannot be deleted
A region still referenced by a customer or user scope is rejected by the API.
Reassign those scopes first with dci update-customer-geographic-access-scope
or dci update-user-geographic-access-scope, or clear them with the matching
delete-*-geographic-access-scope command.
Examples
# Preview the deletion without sending a request.
dci delete-geographic-access-custom-region <custom-region-id> --dry-run
A local preview of the operation; nothing is deleted.
# Delete without the confirmation prompt, for scripts.
dci delete-geographic-access-custom-region <custom-region-id> --yes
Exit code 0 and no output; the region disappears from `dci list-geographic-access-custom-regions`.
Output
On success, this command produces no response data.
Errors
On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.
HTTP status to exit code mapping
| HTTP status | Exit code | Error code | Meaning |
|---|---|---|---|
| 400 | 30 | VALIDATION_ERROR | The arguments or request body were rejected. Review the command's flags and payload. |
| 401 | 10 | AUTHENTICATION_FAILED | Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY. |
| 403 | 11 | PERMISSION_DENIED | The DoiT user or the active customer context does not have access. |
| 404 | 20 | RESOURCE_NOT_FOUND | The requested resource does not exist. Check the identifier argument. |
| 409 | 21 | RESOURCE_CONFLICT | The operation conflicts with the resource's current state. |
| 429 | 50 | RATE_LIMITED | Too many requests. Retryable — the CLI reports the server-provided delay. |
| 500, 503 | 40 | API_SERVER_ERROR | The API failed to process the request. Retryable; contact DoiT support if it persists. |
Related
- list-geographic-access-custom-regions — List custom regions
- get-geographic-access-custom-region — Get a custom region
- update-geographic-access-custom-region — Update a custom region
- create-geographic-access-custom-region — Create a custom region
- API reference: DELETE /rbac/v1/custom-regions/{customRegionId}
Aliases: deletegeographicaccesscustomregion