[Feature Request] View Exported Event Histories in Local Server
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 379
- Forks
- 103
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Description
Is your feature request related to a problem? Please describe.
Customers often want to be able to take an exported event history (either self hosted or cloud) and view it after the fact for audit purposes. There currently isn't a great way of doing this easily, and the Temporal CLI would be a natural place for this.
Describe the solution you'd like
I'd like to be able to take a history export, download it, run the Temporal CLI with a flag --history and view it in the Temporal WebUI. This could either be part of the main CLI or a CLI extension. If a codec server is needed to decrypt, the mechanisms are already in place.
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 by reading the Temporal CLI command and flag handling, then inspect the existing codec-server mechanisms referenced in the issue. Determine how an exported history can be supplied to a local server and displayed in the Temporal WebUI, whether as a main CLI feature or extension. Done means the --history workflow can load an exported history, use the codec server when needed, and make it viewable for audit purposes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100