temporalio / temporalio/temporal
Allow configurable root path for HTTP API
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
Even though our server API only listens to /namespaces, /cluster, and /system-info, some users may still want that at a deeper level (as opposed to their proxies trimming it off), so allow users to specify a path prefix.
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 locating the HTTP API route registration for /namespaces, /cluster, and /system-info, then trace how server configuration is defined and applied. Implementing this should allow a user-specified path prefix while preserving the API routes beneath it; verify the configured and default paths if existing tests cover them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100