Skip to content

Special behavior for Temporal built-in prefixes #576

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
6 of 9 tasks
cretz opened this issue Jan 14, 2025 · 1 comment
Open
6 of 9 tasks

Special behavior for Temporal built-in prefixes #576

cretz opened this issue Jan 14, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@cretz
Copy link
Member

cretz commented Jan 14, 2025

Describe the solution you'd like

All SDKs need to do the following:

  • Disallow workflows, activities, Nexus operations/services, task queues, signals, queries, and updates to be registered that start with __temporal_
  • Disallow queries to be registered that equal __stack_trace or __enhanced_stack_trace
  • Do not call dynamic handlers with reserved names
  • For any query that does match the above pattern, it should be handled without going through interceptors (this means that it no longer appears in tracing for instance) [should apply to everything except Go/Java]

Per-SDK Tickets

@Sushisource
Copy link
Member

Disallowing reserved prefixes on Task Queues should happen in Core for those SDKs

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants