temporalio/cli

Is your feature request related to a problem? Please describe. We are too assumptive about JSON usage everywhere...We need to support arbitrary encodings for at least inputs (if not outputs also...) , for example encoding=json/protobuf. We support this on some commands while others we do not. Describe the solution you'd like Support protobufs for real from the CLI since we include it as default data converter in most SDKs OOTB. We really should allow specifying the OUTPUT encoding too since protobufs are a result too, not just an input. Basically, these commands need to be consistency and real-world. Additional context I did the hard part for you in identifying which commands lack proper support for input encoding: Category Command Payload Flag Meta/Encoding Switch? Workflow start / execute --input Yes (--input-meta) Workflow update start --input Yes (--input-meta) Workflow signal --input No Workflow query --input No Activity complete --result No Activity fail --detail

Describe the bug Fetching workflow update result via temporal workflow update execute or temporal workflow update result with -o json yields output that is incorrect in two ways: If there is the update failed with an error, no error JSON is produced. If the update succeeds, the JSON does not include full result payload details when using the --no-json-shorthand-payloads option (it is effectively silently ignored). Minimal Reproduction Failed update Start this workflow @workflow.defn class WorkflowWithUpdate: @workflow.run async def run(self) -> None: await asyncio.Future() @workflow.update async def update(self) -> str: raise ApplicationError("error in update") temporal workflow start --type WorkflowWithUpdate --task-queue demo Now try to fetch an update result. The CLI outputs an error message but no JSON error info. It should output detailed structured error chain info including stack traces: $ temporal workflow -o json update execute --workflow-id