temporalio / temporalio/temporal
Support Environment Variable Substitution for clusterMetadata in Temporal Configuration Templates
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Currently, Temporal’s template configuration does not support substituting environment variables in the clusterMetadata section. This limitation makes it difficult to dynamically configure multi-cluster setups or enable/disable features like enableGlobalNamespace without manually modifying the configuration file.
Expected Behavior:
- Support for environment variables within the clusterMetadata section.
- Ability to set dynamic cluster configurations (e.g., enable global namespaces, multi-cluster addresses) through environment variables.
Example:
clusterMetadata:
enableGlobalNamespace: {{ env "TEMPORAL_CLUSTER_METADATA_ENABLE_GLOBAL_NAMESPACE" | default "false" }}
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 Temporal configuration template renderer and the path that processes clusterMetadata. Review how environment substitution currently works in other configuration sections, then add coverage for the provided enableGlobalNamespace example and dynamic multi-cluster values. Done means clusterMetadata accepts environment substitutions without manual configuration edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100