list-cloud-diagram-node-activities

dci list-cloud-diagram-node-activities [flags]

Returns individual activity records for the specified component node, ordered by timestamp descending.

Paging

This endpoint pages with --limit and --offset, not page tokens, so --all does not apply.

Examples

# The change history of one component node, newest first (50 by default).
dci list-cloud-diagram-node-activities --ss-id <layer-id> --node-id <node-id>

# The next 50, as JSON.
dci list-cloud-diagram-node-activities --ss-id <layer-id> --node-id <node-id> --offset 50 --output json

Flags

Flag	Type	Default	Example	Description
--ss-id	string			Layer ID.
--node-id	string			Node component ID.
--limit	integer			Maximum number of records to return (default 50).
--offset	integer			Number of records to skip (default 0).

Every command also accepts the CLI-wide flags for output shaping — see Output formats and Table output options.

Output

OK - Node activity records 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
[]._id	string	Activity record ID.
[].activity	string	Activity type. One of: "NODE_CREATE", "NODE_UPDATE", "NODE_DELETE".
[].metadata	object	Activity-specific payload (structure varies by activity type).
[].timestamp	string (date-time)	Timestamp of the activity.
[].user	string	ID of the user who performed the activity.
[].statussheet	string	Layer ID where the activity occurred.

Raw JSON schema

{
  "type": "array",
  "items": {
    "type": "object",
    "required": [
      "_id",
      "activity",
      "timestamp",
      "user",
      "statussheet"
    ],
    "description": "An individual activity record scoped to a specific component node.",
    "properties": {
      "_id": {
        "type": "string",
        "description": "Activity record ID."
      },
      "activity": {
        "type": "string",
        "enum": [
          "NODE_CREATE",
          "NODE_UPDATE",
          "NODE_DELETE"
        ],
        "description": "Activity type."
      },
      "metadata": {
        "type": "object",
        "additionalProperties": true,
        "description": "Activity-specific payload (structure varies by activity type)."
      },
      "timestamp": {
        "type": "string",
        "format": "date-time",
        "description": "Timestamp of the activity."
      },
      "user": {
        "type": "string",
        "description": "ID of the user who performed the activity."
      },
      "statussheet": {
        "type": "string",
        "description": "Layer ID where the activity occurred."
      }
    }
  }
}

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.

Related

• list-cloud-diagram-activity-groups — List activity groups for a layer
• get-statussheet-components — Get layer components
• search-cloud-diagrams — Search diagrams and components
• API reference: GET /clouddiagrams/v1/activity/node-activities

Aliases: listclouddiagramnodeactivities