Closed cretz closed 1 week ago
After some discussion internally and on #608, here is what we're thinking:
--event-details
and continue to default to 3-column table output by default--detailed
option that, when provided, now does events as sections
--------------- [<event_id>] <event_type> ---------------
.
delimited fields, skipping empty
fields, no quotes, sorted, and with event-level fields merged with the attribute level fieldsHere is an example of --detailed
output:
--------------- [1] WorkflowExecutionStarted ---------------
attempt: 1
eventId: 1
eventTime: 2024-06-27T23:42:00Z
eventType: WorkflowExecutionStarted
firstExecutionRunId: 6b8b1127-af83-4329-a327-2a22ec88c4a7
firstWorkflowTaskBackoff: 0s
identity: 904724@antlai-tp1
input.payloads[0]: Temporal
originalExecutionRunId: 6b8b1127-af83-4329-a327-2a22ec88c4a7
taskQueue.kind: TASK_QUEUE_KIND_NORMAL
taskQueue.name: hello-world
workflowId: workflow-RdV-QSRE-Ls9zQosf80cw
workflowTaskTimeout: 10s
workflowType.name: example
--------------- [2] WorkflowTaskScheduled ---------------
attempt: 1
eventId: 2
eventTime: 2024-06-27T23:42:00Z
eventType: WorkflowTaskScheduled
startToCloseTimeout: 10s
taskQueue.kind: TASK_QUEUE_KIND_NORMAL
taskQueue.name: hello-world
Describe the solution you'd like
Do after #545. Previous 0.11.0 CLI had the
Details
column ofworkflow show
a bit more readable than current. See if we can make current more readable.