[DRIVERS-2749] [Astrolabe] Investigate using Local Deployments from the Atlas CLI Created: 18/Oct/23 Updated: 30/Nov/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Astrolabe, Atlas Testing |
| Fix Version/s: | None |
| Type: | Task | Priority: | Unknown |
| Reporter: | Steve Silvester | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Driver Changes: | Not Needed |
| Description |
SummaryWe have had significant issues with handling Atlas infrastructure in our Astrolabe tests ( What is the problem or use case, what are we trying to achieve? MotivationBy using local Atlas deployments, we can be immune to outages, and ensure that resources are confined to the EVG task. Who is the affected end user?DBX Drivers teams. How does this affect the end user?Failing tests, increased cost, maintenance burden. Is this issue urgent?No Is this ticket only for tests?Yes Acceptance CriteriaAstrolabe tests use. |