temporalio / temporalio/temporal
access from one temporal namespace to another
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
hello, I was wondering if there any additional considerations when referencing resources from one namespace to another?
For instance:
lets say I workflow_1 that contains activity_1 and resides in temporal namespace_1
and I also have namespace_2 which contains workflow_2 and activity_2
and both temporal namespaces, namespace_1 and namespace_2, exist in the same temporal server
would we run into any issues if the inputs for activity_2 depends on outputs from activity_1? I'm not sure if temporal namespaces behave like k8s namespaces as far as access
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
The issue names no files, tests, or entry points. First determine how Temporal namespaces scope workflows, activities, and cross-namespace access, then confirm whether activity_2 can consume activity_1 output when both namespaces share a server. Done means documenting the supported behavior and any required access or configuration considerations.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100