[Bug] Deprecate cross-namespace support in workflow commands/events
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 133
- Forks
- 101
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 11
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.
Contributor guide
No contributing guide indexed for this repository
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 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.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100