fix(recommendations): parseMemoryDBDetails uses rec fields, errors loudly on empty (closes #378)#539
Conversation
…ors loudly on empty Previously, the function either hardcoded db.r6gd.xlarge (original) or silently returned nil without populating Details (feat branch). Both paths caused MemoryDB RI purchases to silently fail when the rec's actual instance type was anything other than the hardcoded default. Now the function errors loudly when rec.ResourceType is empty (so the recommendation is logged as a warning by parseRecommendations and skipped), and populates CacheDetails correctly when ResourceType is set. Also removes the unused log import and updates TestParseMemoryDBDetails to cover the empty-ResourceType error path and two valid instance types. Closes #378
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough
ChangesMemoryDB Detail Parsing
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Hand-off PR for partially-completed work from a sub-agent that hit a usage cap.
parseMemoryDBDetailspreviously hardcodeddb.r6gd.xlarge / redis, silently failing every non-default MemoryDB RI purchase. Single commit makes it readrec.ResourceTypeand error loudly when empty. \n\nCloses #378.Summary by CodeRabbit
Release Notes