[SERVER-61429] Ensure tenantId "" is prohibited Created: 11/Nov/21 Updated: 27/Oct/23 Resolved: 15/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Participants: |
| Description |
|
Since we're using "" as the internal tenantId for protocol "shard merge", let's make donorStartMigration / recipientSyncData ban tenantId as a caller-provided tenantId with protocol "multitenant migrations". |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 15/Nov/21 ] |
|
Thanks suganthi.mani. |
| Comment by Suganthi Mani [ 15/Nov/21 ] |
|
We already have the logic to prevent callers from providing tenantId as "" for donorStartMigration / recipientSyncData command. |