-
Type:
Task
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Serverless
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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".