[Bug] Deprecate cross-namespace support in workflow commands/events
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, grpc
- Domain
- api, backend-api-design
Research direction
Start in the API definitions for workflow commands and their event counterparts, and locate each namespace property mentioned in the issue. Deprecate those properties while preserving existing cross-namespace support through the system.enableCrossNamespaceCommands configuration; completion means the affected API fields clearly communicate their deprecated status.
Written by the indexing model from the issue text.
Description
Describe the bug
Temporal Server 1.30.0 disabled support for cross-namespace workflow commands (i.e. starting a child workflow in a different namespace) by default due to security and reliability concerns. Admins must now explicitly set the system.enableCrossNamespaceCommands dynamic configuration to allow such operations.
This change should be reflected into SDKs by deprecating the namespace property on various workflow commands (and their events counterpart). There is no immediate desire to pull the plug on actual support of cross-namespace operations besides the existing system.enableCrossNamespaceCommands configuration, but we want to clearly communicate the intent that this property should not be used going forward.
- Dominant language
- Go
- Stars
- 134
- Forks
- 104
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from temporalio/api
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/api#427 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
temporalio/api#421 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/api#400 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
temporalio/api#328 · 6 reactions ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
temporalio/api#307 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
resend/resend-skills#144 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cloudnativelabs/kube-router#2189 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
🕷️ bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sysadminsmedia/homebox#1770 ·
Maintainers usually reply within 2 days