Repository navigation
refactor(aws/recommendations): extract generic fetchWithRetry for CE page fetchers - #607
Merged
Merged
Conversation
…page fetchers fetchCoveragePage, fetchUtilizationPage, fetchSPCoveragePage and fetchSPUtilizationPage were four copies of the same rate-limit, concurrency and retry loop. They now delegate to one generic helper with unchanged behaviour and error messages. Part of #120. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Member
Author
Merge gate verdict (claude-cc-libs)Every gate holds at head 573985d:
CodeRabbit is waived as a merge gate under the 2026-10-19 decision. Squash-merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #120.
What
Extracts a generic
fetchWithRetryhelper inproviders/aws/recommendationsand routesfetchCoveragePage,fetchUtilizationPage,fetchSPCoveragePageandfetchSPUtilizationPagethrough it. Behaviour and error messages are unchanged; four unit tests cover retry-then-success, terminal-error wrapping, max-retries and a canceled context.Already done on main
Remaining slices of #120
providers/awswith the CI-pinned golangci-lint and record the breakdown.nolint.fetchRIPageWithRetry,fetchSPPageWithRetryandfetchOnDemandPageinto the same helper (they differ in error text and retry-count reporting).Verified with and without
GOWORK=off: build, vet,go test -count=1 ./..., golangci-lint (0 issues).🤖 Generated with Claude Code
Summary by CodeRabbit