delete-user
dci delete-user <id>
Deletes a user.
id— User ID as shown bydci list-users(theidfield). This also removes the retained row of a cancelled invite. Users are not resolved by name; pass the ID.
Examples
# Preview what would be deleted without sending a request.
dci delete-user <user-id> --dry-run
# Delete the user without an interactive prompt, for scripts.
dci delete-user <user-id> --yes
Output
OK - User deleted successfully.
By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.
| Field | Type | Description |
|---|---|---|
message | string | Success message |
Raw JSON schema
{
"type": "object",
"description": "Response confirming user deletion.",
"properties": {
"message": {
"type": "string",
"description": "Success message"
}
}
}
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. |
| 500 | 40 | API_SERVER_ERROR | The API failed to process the request. Retryable; contact DoiT support if it persists. |
Related
- list-users — List users
- update-user — Update user
- cancel-invite — Cancel invite
- invite-user — Invite user
- API reference: DELETE /iam/v1/users/{id}
Aliases: deleteuser