temporalio / temporalio/temporal
Support bypass of autoforwarding with special header
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Currently when autoforwarding is on for all apis, it would be hard to investigate standby cluster/workflow issues (because all requests goes to active cluster)
Describe the solution you'd like
A clear and concise description of what you want to happen.
Some way to bypass autoforwarding. This is mostly need for debugging/investigation purpose
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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 tracing the service's autoforwarding path for API requests and how requests are routed between active and standby clusters. Define and implement the requested special-header behavior so debugging requests can bypass autoforwarding, then verify that ordinary requests still forward as before.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100