get-cloud-incident

dci get-cloud-incident id

Returns the specified cloud incident.

Output

OK - Cloud incident returned.

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
`createTime`	integer (int64)	The time when this cloud incident was created, in milliseconds since the epoch.
`description`	string	Detailed explanation on the cloud incident.
`id`	string	The unique id of a cloud incident
`platform`	string	The cloud platform. One of: `"google-cloud"`, `"amazon-web-services"`.
`product`	string	The name of the product affected by the cloud incident
`status`	string	The Status of the issue One of: `"active"`, `"archived"`.
`summary`	string	A summary of the cloud incident.
`symptoms`	string	Cloud incident symptoms, if available.
`title`	string	Cloud incident name provided by the cloud vendor.
`workaround`	string	Mitigation workaround for the cloud incident, if available.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "createTime": {
      "type": "integer",
      "description": "The time when this cloud incident was created, in milliseconds since the epoch.",
      "format": "int64"
    },
    "description": {
      "type": "string",
      "description": "Detailed explanation on the cloud incident."
    },
    "id": {
      "type": "string",
      "description": "The unique id of a cloud incident"
    },
    "platform": {
      "type": "string",
      "description": "The cloud platform.",
      "enum": [
        "google-cloud",
        "amazon-web-services"
      ]
    },
    "product": {
      "type": "string",
      "description": "The name of the product affected by the cloud incident"
    },
    "status": {
      "type": "string",
      "description": "The Status of the issue",
      "enum": [
        "active",
        "archived"
      ]
    },
    "summary": {
      "type": "string",
      "description": "A summary of the cloud incident."
    },
    "symptoms": {
      "type": "string",
      "description": "Cloud incident symptoms, if available."
    },
    "title": {
      "type": "string",
      "description": "Cloud incident name provided by the cloud vendor."
    },
    "workaround": {
      "type": "string",
      "description": "Mitigation workaround for the cloud incident, if available."
    }
  }
}

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	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.

Aliases: get-known-issue

Output​

Errors​

Output

Errors