Skip to main content

delete-customer-geographic-access-scope 

dci delete-customer-geographic-access-scope

Clears the geographic scope for a target customer, leaving it unassigned. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Repeating the request is idempotent. Requires the UsersManager permission.

Examples​

# Preview clearing a customer's geographic scope without sending a request.
dci delete-customer-geographic-access-scope <target-customer-id> --dry-run
A local preview of the operation; the scope is unchanged.
# Clear the scope without the confirmation prompt, for scripts.
dci delete-customer-geographic-access-scope <target-customer-id> --yes
Exit code 0 and no output; `dci get-customer-geographic-access-scope <target-customer-id>` now reports `type: unassigned`.

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: deletecustomergeographicaccessscope