This message was deleted.

What did you have in mind? I assume you’re referring to the resource.metadata section? We recently added some fields related to VCS systems to the projects.metadata section

yes, the resources.metadata section. We’re planning to use the json output to render price breakdowns on a UI, and we’d like to add a mapping from the resource to an id in our catalog.

So far we’ve been putting those kinds of things in brackets in cost component names, e.g.

Instance usage (Linux/UNIX, reserved, t3.medium)

Longer term we want to make those key=value pairs in the JSON resource.metadata as it enables a more robust way to parse what’s changed in the

infracost diff

format (notice the →)

~ Instance usage (Linux/UNIX, on-demand, m5.4xlarge → m5.2xlarge)

It would be interesting to see if others in this channel have similar use-cases as you for the resource.metadata section.

yes, that sounds perfect!

Would you be willing to share your PR with me, so I can possibly add IBM to my pulumi PR at the same time?

Hey, it’s a crude proof of concept that we tried, in our fork here https://github.com/IBM-Cloud/infracost/blob/master/internal/providers/terraform/ibm/ibm_is_vpc.go#L24 that you’re welcome to see