Repository navigation
chore(providers/aws): periodic audit of findOfferingID across 7 services (closes #515) - #815
Conversation
|
@coderabbitai review |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 7 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
✅ Actions performedReview triggered.
|
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
@coderabbitai review |
Rate Limit Exceeded
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
82a4251 to
dd69c33
Compare
Add context-cancellation and empty-NextToken pagination tests for findOfferingID across 7 AWS services (EC2, ElastiCache, MemoryDB, OpenSearch, RDS, Redshift, SavingsPlans). Also adds AUDIT.md recording the audit findings and pagination contract. Resolves conflict with main's TestPurchaseCommitment_TagFailure_StructuredLog by including both that test and the new findOfferingID tests.
|
Rebased onto origin/main, all CI checks passed, squash-merged. |
Summary
findOfferingID(EC2, RDS, ElastiCache, MemoryDB, OpenSearch, Redshift, SavingsPlans) against the contract established in PR fix(purchases): narrow Describe*Offerings + cap pagination (#688) #690: typed fields, ctx.Err() check, page cap, per-page log, variant soft-skip, nil+empty token terminator.execIDarg in RDS, Redshift, SavingsPlans test calls) are fixed.providers/aws/services/AUDIT.mddocuments the 6-item contract, per-service status table, watchlist (MemoryDB Valkey engine split, OpenSearch/Redshift Graviton dimension), and quarterly audit procedure.TestFindOfferingID_CtxCancelledBeforePageandTestFindOfferingID_EmptyStringTokenEndsPaginationto every service's test file (14 new tests across 7 packages) to pin contract items C2 and C6 against future regressions.Test plan
go test ./providers/aws/services/...-- 319 tests pass across all 7 packagesgo build ./...-- cleanproviders/aws/services/AUDIT.mdfor completeness and accuracy