delete-datahub-dataset

dci delete-datahub-dataset <name>

Deletes a specific DataHub dataset.

• name — Dataset name as shown by dci list-datahub-datasets. The name is the dataset's identifier; there is no separate ID.

Examples

# Preview what would be deleted, without sending a request.
dci delete-datahub-dataset <dataset-name> --dry-run

# Delete the dataset and its events without a prompt, for scripts and CI (interactive terminals ask first).
dci delete-datahub-dataset <dataset-name> --yes

Exit code 0 and no output; `dci list-datahub-datasets` no longer lists the dataset.

Output

OK - Dataset 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

Raw JSON schema

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "example": "Dataset deleted successfully"
    }
  }
}

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.
404	20	RESOURCE_NOT_FOUND	The requested resource does not exist. Check the identifier argument.
500	40	API_SERVER_ERROR	The API failed to process the request. Retryable; contact DoiT support if it persists.

Related

• delete-datahub-datasets — Delete datasets
• delete-datahub-events-by-filter — Delete specific events
• list-datahub-datasets — List datasets
• get-datahub-dataset — Retrieve a dataset
• API reference: DELETE /datahub/v1/datasets/{name}

Aliases: deletedatahubdataset