temporalio / temporalio/temporal
Provide user identity on user-initiated events
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Describe the solution you'd like
Need something like HistoryEvent.user_identity that is set for any events that are initiated by users (so signals and cancellation requests and such, but not timer firing). Up to implementer on details like field name and whether it's optional on top-level events or copied to many specific events. This should only be settable by server as the literal user identity which is assumed to be in context and work in a common way for OSS authorizers and cloud users. This is completely unrelated to existing identity (aka "client identity" or "worker identity") fields.
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
Begin by locating HistoryEvent and the existing identity fields in the Temporal service. Determine how user-initiated events such as signals and cancellation requests are represented, then define the server-provided identity contract and how it differs from client or worker identity. Done should include an agreed design and coverage for all applicable event types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100