This message was deleted.
# help
b
This message was deleted.
j
One thing I noticed is that in the code, the attribute filter is for
Storage-ShardHour
(as an example for 1 attribute). I am checking the pricing data in Postgres, and it’s only called that in
us-east-1
. In other regions, there is a prefix, e.g.
EUC1-Storage-ShardHour
. I wonder if the filter is doing a full match or a partial match...
I’ve tested my theory by tweaking the data:
Copy code
UPDATE products
SET attributes = JSONB_SET(attributes, '{usagetype}', '"Storage-ShardHour"', false)
WHERE attributes->>'usagetype' = 'EUC1-Storage-ShardHour';
I can confirm that after this change, the shard-hour cost changed from $0 to the correct value. Will submit an issue on GitHub.
c
Hey Nick, thanks again for the report. The fix will go out in the 10.31 release. If you’re using the github/lab app, it should be fixed now.