This message was deleted.

Hi @big-library-56813 - great question! In the reference usage-file we don’t have that resource as we didn’t think of that edge-case when defining that resource’s pricing. This is the schema that’s used to define that’s resource’s prices, we’d need to add a string address_type param, similar to something like this, so users can define that in the usage-file. Plz let us know if this is something you’d like to work on and the team’ll be happy to help

yes, that will help. We’d like to show the planned cost based on a certain situation to help the users get a basic understanding of their cost. Although the use case of IP address can change dynamically, it will be better considered in runtime cost.

Hey @big-library-56813! If Ail's proposed solution works for your case, are you willing to make the change for the resource? We have a section in our contributing guide how to do it: https://github.com/infracost/infracost/blob/master/contributing/add_new_resource_guide.md#add-usage-based-cost-components.

That’s awesome Vadim! I wonder if we should put the type in brackets: IP address (standard VM) or IP address (preemptible VM) or IP address (unused)

Sure thing, I'll update it 👍