Skip to main content

delete-allocation 

dci delete-allocation <id>

Deletes the allocation specified by the Id.

  • id — Allocation ID or name as shown by dci list-allocations. Names resolve (exact, unique substring, or close typo); the confirmation shows the resolved target.
Allocations in use cannot be deleted

The API answers 409 Conflict when the allocation is still used by other resources. The error body lists each referencing resource with its id, name, and owner; remove those references first, then delete again.

Examples​

# Preview what would be deleted, without sending a request.
dci delete-allocation "Team Backyard" --dry-run
# Delete without a prompt, for scripts and CI (interactive terminals ask first).
dci delete-allocation <allocation-id> --yes
Exit code 0 and no output; `dci list-allocations` no longer lists the allocation.

Output​

OK - Allocation deleted.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Returns: object

Example response (--output json)​

{}
Raw JSON schema
{
  "type": "object",
  "additionalProperties": false
}

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.

Aliases: deleteallocation