Recently the Azure costs api has shown occasional behaviour where some costs are duplicated. Our handling of dupes assumes all costs are duplicated, so this should be updated to handle this new behaviour as well.
This will require a custom filtering of dupes as a simple .uniq is likely to be too intensive, as there can be a very large number of cost entries involved.
Recently the Azure costs api has shown occasional behaviour where some costs are duplicated. Our handling of dupes assumes all costs are duplicated, so this should be updated to handle this new behaviour as well.
This will require a custom filtering of dupes as a simple
.uniqis likely to be too intensive, as there can be a very large number of cost entries involved.