This message was deleted.
# contributors
b
This message was deleted.
l
@broad-addition-19827 can you have a look when you get a chance? I think you probably know the most about this resource.
b
Yeah, I’ll look at it. Just do not understand why it worked yesterday and fails now without any changes 🤷‍♀️
l
hmm, could be a change from the Azure data
b
I checked it in pricing.api and it’s looks like there are no cost component for Hot RA-GRS Write Operations, but locally in DB it exists. 🙃 I can change RA-GRS to GRS for it, as they got the same prices if you do not mind
And local Write Operation’s priceHash uses for List and Create Operations now 🤕
l
interesting, I'll take a quick look. What queries are you using for the DB?
b
It is current cost component in Mongo:
db.products.find({ 'prices':{ $elemMatch: {'priceHash': '58954c1c2caba89f17c77cfcd73cd9c6-49c37505210dfd1c98233191a87608bd'}}}).pretty()
It is Query Variables I used for pricing.api to see all RA-GRS cost components:
{
"priceFilter": {
"purchaseOption": "Consumption"
},
"productFilter": {
"service": "Storage",
"productFamily": "Storage",
"region": "eastus",
"attributeFilters": [
{
"key": "productName",
"value": "Blob Storage"
}, {
"key": "skuName",
"value": "Hot RA-GRS"
}
]
}
}
Or u can find it by this:
db.products.find({'attributes.meterName': { $regex: "Write Operations", $options: 'i' }, 'attributes.productName': "Blob Storage", 'attributes.skuName': "Hot RA-GRS", service: "Storage", region: "eastus"}).pretty()
l
Thanks. Yeah this is an odd one. It seems like they're using the same meterId, but have just renamed it since the Hot RA-GRS "Write Operations" and "List and Create Operations" are the same price, so they must have them as the same record in their DB. I think the correct fix here would be to use "List and Create Operations" for the metername for Hot RA-GRS.