[DRIVERS-2827] Use Cloud-QA for Lambda Automated Testing Created: 06/Feb/24 Updated: 06/Feb/24 |
|
| Status: | Needs Triage |
| Project: | Drivers |
| Component/s: | Evergreen Tools |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Durran Jordan | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Driver Changes: | Needed - No Spec Changes |
| Description |
SummaryCurrently the drivers automated Lambda testing scripts set up clusters in Atlas prod. These should be changed to use cloud-qa. See: https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/atlas/setup-variables.sh#L20 MotivationWho is the affected end user?Drivers performing AWS Lambda automated testing. How does this affect the end user?Drivers team Atlas budget runs over periodically. How likely is it that this problem or use case will occur?Will be seen often when clusters are not terminated in a timely fashion. If the problem does occur, what are the consequences and how severe are they?Drivers project goes over budget. Is this issue urgent?TBD Is this ticket required by a downstream team?No Is this ticket only for tests?Yes - for drivers automated Atlas testing. Acceptance Criteria
|