Currently, we only support aws and gcp pricing (represented by --cloud). We have already generated the pricing structures for aws/gcp in /pricing, so adding azure shouldn't be that bad.
There might be some regex match stuff that needs to be added to the main cost analysis codepath, but really our locality matching logic is pretty cloud agnostic. Adding an option for azure should entail similar work within the main codepath as running the tool with --pricePath set to azure data.
Currently, we only support aws and gcp pricing (represented by
--cloud). We have already generated the pricing structures for aws/gcp in/pricing, so adding azure shouldn't be that bad.There might be some regex match stuff that needs to be added to the main cost analysis codepath, but really our locality matching logic is pretty cloud agnostic. Adding an option for azure should entail similar work within the main codepath as running the tool with
--pricePathset to azure data.Data rates: https://azure.microsoft.com/en-us/pricing/details/bandwidth/
Looks similar to GCP, looks like we can just modify the
gcp_rate_converter.goscript to match azure localities.