Use catalog information in EntityInfraWalletCard

[swnia]

It would be great to be able to use the information in the catalogue to be able to fetch the relevant information for an entity.
Currently, I do not have a concrete idea how to tackle this and whether this is something others might benefit from.
Ideas were to introduce another annotation that supports a catalog query or to automatically query the related entities based on a configurable kind and/or spec.type.

[gluckzhang]

Interesting idea. Do you mean, for example, we can filter catalog entities by their daily cost? I am not sure how complex it will be, because catalog entities are synced periodically from different sources. Does this feature require InfraWallet to add cost annotations to these catalog entities? To be further investigated.

[swnia]

That might be interesting, too!

I thought to just be able to use information tracked in the catalog (i.e. Kubernetes clusters) that an entity depends on to use to lookup the associated project/account (or if these are tracked in the catalog directly those) for displaying cost in the EntityInfraWalletCard rather than filling in the infrawallet.io/account and infrawallet.io/project manually.

[gluckzhang]

That might be interesting, too!

I thought to just be able to use information tracked in the catalog (i.e. Kubernetes clusters) that an entity depends on to use to lookup the associated project/account (or if these are tracked in the catalog directly those) for displaying cost in the EntityInfraWalletCard rather than filling in the infrawallet.io/account and infrawallet.io/project manually.

Oh I see, like using some well-known annotations in the catalog entities and try to query the cost from InfraWallet right? If the information is sufficient for an accurate query, that would be great. For example, not only K8s cluster information is needed, but also its provider and project information. That would be nice if you could share some examples about these catalog entities that you would like to associate costs directly. On a Backstage entity page, you can click the three-dot button at the upper right corner of the page and click Inspect entity to get the yaml definition of that entity.

[swnia]

So, we also track our accounts/projects in backstage which would make this particularly easy for us 🙂 but Kubernetes Clusters are well defined and the Dashboard URL annotation could be used for this.

As an alternative, we could define a new API endpoint like /entityreports which by default just calls the current /reports functionality but allows defining a custom function through a novel infraWalletEntityReportsExtensionPoint (name up for discussion 😄 ) that could take the entity as an input.