[CLI Refresh] Consistent payload input options across all commands
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Go
- Stars
- 379
- Forks
- 103
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Description
Workflow input payload supports options including
-i, --input stringArray Input value (default JSON unless --input-payload-meta is non-JSON encoding). Can be given multiple times for multiple arguments. Cannot be combined with --input-file.
--input-base64 If set, assumes --input or --input-file are base64 encoded and attempts to decode.
--input-file stringArray Reads a file as the input (JSON by default unless --input-payload-meta is non-JSON encoding). Can be given multiple times for multiple arguments. Cannot be combined with --input.
--input-meta stringArray Metadata for the input payload. Expected as key=value. If key is encoding, overrides the default of json/plain.
Extend this to make payload functionality uniform across other payloads inputs such as Activity result, Activity failure detail.
Ref https://github.com/temporalio/cli/pull/445#discussion_r1486903085
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing workflow input payload option handling and review the linked pull request discussion. Trace the commands that accept Activity results and Activity failure details, then compare their payload flags and parsing paths. Done means the supported input, file, base64, and metadata options are consistent across the identified payload inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100