[SERVER-80126] Make TenantDatabaseCloner use DatabaseName obj Created: 16/Aug/23 Updated: 29/Oct/23 Resolved: 30/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ntdi_must_have | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Server Serverless 2023-09-04 | ||||||||
| Participants: | |||||||||
| Description |
|
The TenantDatabaseCloner will not run in multitenancy environment and we don't worry about dropping tenant by accident when string db is used for this class. But, as we decide to pass the db name with DatabaseName object around in the code base to decrease the code complex for engineers, we still need to change its constructor to take in DatabaseName object and perhaps also change its structure to hold DatabaseName object too. |
| Comments |
| Comment by Githook User [ 29/Aug/23 ] |
|
Author: {'name': 'Mathis Bessa', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |