test(cmd): existing tests reach real AWS endpoints #2162
Copy link
Copy link
Open
Labels
effort/mDaysDaysimpact/internalTeam-internal onlyTeam-internal onlypriority/p2Backlog-worthyBacklog-worthyseverity/mediumModerate harmModerate harmtriagedItem has been triagedItem has been triagedtype/bugDefectDefecturgency/this-quarterWithin the quarterWithin the quarter
Description
Activity
- addedtriagedItem has been triagedItem has been triagedpriority/p2Backlog-worthyBacklog-worthyseverity/mediumModerate harmModerate harmurgency/this-quarterWithin the quarterWithin the quarterimpact/internalTeam-internal onlyTeam-internal onlyeffort/mDaysDaystype/bugDefectDefect
on Oct 9, 2026
Metadata
Metadata
Assignees
Labels
effort/mDaysDaysimpact/internalTeam-internal onlyTeam-internal onlypriority/p2Backlog-worthyBacklog-worthyseverity/mediumModerate harmModerate harmtriagedItem has been triagedItem has been triagedtype/bugDefectDefecturgency/this-quarterWithin the quarterWithin the quarter
TestProcessService_SavingsPlansAccountLevel, TestRunToolFromCSV* and TestCSVCap* build real AWS clients and send requests to the live endpoints (IMDS and service endpoints; they fail with credential errors and slow the package to about 8 minutes). Reproduced on base 22126ab as well as on #2160. They should use a stubbed transport (see spStubTransport in cmd/savings_plan_purchase_test.go) so unit tests never leave the machine. Found while verifying #2160.