Skip to main content

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 statusExit codeError codeMeaning
40030VALIDATION_ERRORThe arguments or request body were rejected. Review the command's flags and payload.
40110AUTHENTICATION_FAILEDNot signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
40311PERMISSION_DENIEDThe DoiT user or the active customer context does not have access.
40420RESOURCE_NOT_FOUNDThe requested resource does not exist. Check the identifier argument.
40921RESOURCE_CONFLICTThe operation conflicts with the resource's current state.
42950RATE_LIMITEDToo many requests. Retryable — the CLI reports the server-provided delay.
500, 50340API_SERVER_ERRORThe API failed to process the request. Retryable; contact DoiT support if it persists.

Aliases: deletegeographicaccesscustomregion