temporalio / temporalio/temporal
Simple configuration structure
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.
The current server configuration takes a directory and an environment name, supports merging multiple files and requires separate files for static and dynamic config.
This complexity hurts the developer experience and is the reason we don't expose server configuration in the Temporal CLI.
Describe the solution you'd like
Come up with a clean config structure that can be contained in a single file.
Additional context
Extra care should be taken if we migrate to a new format to avoid breaking existing users.
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 how the server currently consumes a directory, environment name, merged files, and separate static and dynamic configuration. Then examine how the Temporal CLI could expose that configuration. Done means a defined single-file structure with a migration approach that avoids breaking existing users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100