feat(#217): wire live pricing for internet egress and inter-AZ data transfer - #220
Merged
Conversation
…ransfer The last two seed-only data-transfer metrics now sync live. Both live in the global (region="") AWSDataTransfer catalogue with ONE usagetype per source region (not per region pair like inter-region), so add a second helper, _upsert_regionless_usagetype, driven by a `regionless_usagetype` descriptor flag + `usagetype_base`: - keep every row for the region's usagetype (preserving tiers) and store them under the sync region; - us-east-1 data-transfer usagetypes are unprefixed (AWS legacy quirk), every other region prepends its short prefix. Descriptors added (validated against the live Cloud Pricing API): - DataTransfer-Internet-Out-GB transferType "AWS Outbound", usagetype "DataTransfer-Out-Bytes", tiered $0.09/$0.085/$0.07/$0.05 - DataTransfer-InterAZ-GB transferType "IntraRegion", usagetype "DataTransfer-Regional-Bytes", flat $0.01 End-to-end live check via a real cache+catalog: internet egress 5 TB = $450.00, 20 TB = $1751.20 (spans two tiers); inter-AZ 1000 GB = $10.00. All three DataTransfer metrics now price live. Tests (HTTP mocked): tier preservation for us-east-1 internet egress, correct prefixed-vs-bare usagetype selection for non-us-east-1, inter-AZ flat rate, and descriptor presence. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
elecnix
marked this pull request as ready for review
July 3, 2026 15:40
This was referenced Jul 3, 2026
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
1 participant
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.
Summary
Follow-up to #219. Wires up the last two seed-only data-transfer metrics —
DataTransfer-Internet-Out-GBandDataTransfer-InterAZ-GB— so all three data-transfer metrics now price live.Mechanism
Both live in the global (
region="")AWSDataTransfercatalogue but, unlike inter-region transfer, have one usagetype per source region (not per region pair). So this adds a second helper_upsert_regionless_usagetype, driven by aregionless_usagetypedescriptor flag +usagetype_base:USW1-).Descriptors (validated against the live Cloud Pricing API)
DataTransfer-Internet-Out-GBAWS OutboundDataTransfer-Out-BytesDataTransfer-InterAZ-GBIntraRegionDataTransfer-Regional-BytesLive end-to-end validation (real cache + catalog)
Test plan (HTTP layer mocked)
Existing descriptors and the #219 inter-region path are unaffected (the new flag is optional). Note: the live grouping was confirmed this session; CI runs fully mocked.