temporalio / temporalio/temporal

Enable wildcard namespace definition when setting namespace RPS

Open
#6,237 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
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.
It seems there is a way of setting namespace RPS limits as outlined here. To enable a more dynamic approach, it would be useful to be able to define wildcard rules that get applied to namespaces (e.g. stg-* means any namespaces matching this rule such as stg-test will have this rule applied to it).

Describe the solution you'd like
Current functionality:

frontend.namespacerps:
- value: 2000
- value: 100
  constraints:
    namespace: "namespaceA"
- value: 500
  constraints:
    namespace: "namespaceB"

Requested functionality:

frontend.namespacerps:
- value: 1000
- value: 500
  constraints:
    namespace: "stg-*"
- value: 600
  constraints:
    namespace: "prod-*"

Describe alternatives you've considered
The alternative here is updating the server config every time a new namespace is added to which we want to apply RPS limits. The proposed approach can allow a more generic configuration of RPS limits to namespaces.

Additional context
N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation files or tests are named in the issue. Start by tracing the frontend.namespacerps configuration and namespace RPS matching behavior, then identify where namespace constraints are evaluated. Done means wildcard rules such as stg-* and prod-* apply to matching namespaces without per-namespace configuration updates, with coverage for matching and non-matching names.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.