Repository navigation
Conversation
…wrong engine findOfferingID sent the Cost Explorer ProductDescription verbatim as the engine filter, including an empty value, and the page scan checked only the payment option of the first offering, so an offering for a different engine, node type or term could be bought. Refuse an empty engine with an error naming the missing field, send the engine lowercased as ElastiCache reports it, and fail on a first offering whose node type, duration or engine differs from the request. Other #53 items are not covered here. Part of #53 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
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 #53
What
ElastiCache.findOfferingIDsent the Cost ExplorerProductDescriptionverbatim as the engine filter, including an empty value, andscanElastiCacheOfferingPagechecked only the payment option of the first offering (finding A07-033 and the "ElastiCache offering lookup" item). Now:Why this item: it is the one purchase path where a wrong-product reservation (other engine, node type or term) could be bought on a mismatch or empty filter. Offering price vs approved cost is in #611.
The existing happy-path fixture and one pricing case now carry Duration/ProductDescription or expect the filter-mismatch error (a 3yr offering for a 1yr request is rejected by the scan before pricing).
Not covered (left on #53)
Remaining items other than the SP offering-ID, SP rounding and CE strict validation already merged, and the EC2 price check in #611.
Proof
go test -timeout 300s -count=1 ./..., golangci-lint v2.10.1 with the repo config, gocyclo: clean.🤖 Generated with Claude Code
Summary by CodeRabbit