charmhub incorrectly recognises a charm's substrate

[mthaddon]

Currently https://charmhub.io/nginx-ingress-integrator is listed as "Ubuntu 20.04" in terms of platform. However, this is a k8s charm, as denoted by the following in metadata.yaml:

assumes:
  - k8s-api

[jkfran]

I will repeat here what I said on Mattermost:

The homepage of Charmhub uses the find endpoint from PublisherGW. The find endpoint doesn't provide the content of the metadata.yaml. This endpoint returns a field result.deployable-on which we use to show these icons:

In this case, the value of this field is empty. When this value is empty, we decided to show VM because it was the case for most of the charms. @Roadmaster, could the API consider what Tom mentioned in the metadata.yaml to return "Kubernetes"?

[Roadmaster]

I would like to have some documentation on what the possible values for "assumes" are, before updating the rule that determines deployable-on. Can you or Tom point us to it?

Thanks!

[mthaddon]

All I can find is https://juju.is/docs/sdk/assumes but that doesn't seem to cover all the values (it seems like it can be anything).

[juanmanuel-tirado]

At this point Juju only processes juju and k8s-api assumes AFAIK. See the code here

[Lukewh]

Is this being tracked somewhere else? Happy to leave this issue open until we hear more, but it sounds like there's nothing for the webteam to do for now.

[mthaddon]

@Roadmaster is there an update on this? Should we be tracking the issue elsewhere?

[mthaddon]

@Roadmaster also see https://juju.is/docs/olm/supported-features