delete-customer-notification
dci delete-customer-notification [flags]
Permanently deletes an organization-wide cost-anomaly notification config. Requires the settings (Manage settings) permission and the If-Match header. The Idempotency-Key header is required. The same key, the same body, and the same If-Match replay the stored success. A different body or a different If-Match is 422 idempotency_key_reused. A 5xx response may leave the key reserved, so a retry returns 409 until the original request is released or about 30 minutes pass. dryRun=true does not reserve the key. With dryRun=true the request goes through the same checks as a real delete without deleting anything. Deleting an id that is not a cost-anomaly config, or that no longer exists, returns 404.
Reads are immediately consistent. After a completed delete (204 without X-Dry-Run: true), a GET of that notification returns 404.
Flags
| Flag | Type | Default | Example | Description |
|---|---|---|---|---|
--dry-run | boolean | false | If true, validates the request and returns the would-be result without applying it. The response then carries the X-Dry-Run header. |
Every command also accepts the CLI-wide flags for output shaping — see Output formats and Table output options.
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, 422 | 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. |
| 412, 428 | 1 | API_ERROR | The request failed; the printed error message has details. |
| 500 | 40 | API_SERVER_ERROR | The API failed to process the request. Retryable; contact DoiT support if it persists. |
Related
- create-customer-notification — Create an organization cost anomaly notification
- create-user-notification — Create a personal notification for a user
- delete-user-notification — Delete a personal notification
- get-customer-notification — Get an organization cost anomaly notification
- get-user-notification — Get a personal notification
- list-customer-notifications — List organization cost anomaly notifications
- list-user-notifications — List personal notifications for a user
- update-customer-notification — Update an organization cost anomaly notification
- update-user-notification — Update a personal notification
- API reference: DELETE /customers/v1/notifications/{id}
Aliases: deletecustomernotification