Labelling devfiles in the Dashboard

[sunix]

Is your enhancement related to a problem? Please describe.

In the dashboard get-started page, admin can configure Che to have devfiles coming from different devfile registries. The problem is that it is hard to differentiate where the devfile is coming from.
This is what is done in the Red Hat Developer Sandbox SaaS which is mixing CodeReady Workspaces devfiles and Che community devfiles. It is not possible to distinguish from which registry is coming a devfile. A user may use unwillingly the community one rather than the one from CodeReady Workspaces.
A label showing that a devfile is a "community" devfile would help. Labels could be used in other use cases: showing the supported architectures for instance.

Describe the solution you'd like

The idea is to reuse the field from the meta.yaml file that we have already in the devfile registries: The tags field.
In meta.yaml attributes

displayName: Quarkus Postgresql
description: Build and run hotspot or native Quarkus app with postgresql
tags: ["Community", "arm64", "Airgap", "Java", "Quarkus", "OpenJDK", "Maven", "Native", "GraalVM"]
icon: /images/quarkus.svg
globalMemoryLimit: 8Gi
Links:
  self: /devfiles/quarkus-postgresql/devfile.yaml

In index.json (generated) of the registry

[
...
,
  {
    "displayName": "Quarkus Postgresql",
    "description": "Build and run hotspot or native Quarkus app with postgresql",
    "tags": [
      "Community",
      "arm64",
      "Airgap",
      "Java",
      "Quarkus",
      "OpenJDK",
      "Maven",
      "Native",
      "GraalVM"
    ],
    "icon": "/images/quarkus.svg",
    "globalMemoryLimit": "8Gi",
    "links": {
      "self": "/devfiles/quarkus-postgresql/devfile.yaml"
    }
  },

Based on an operator cluster configuration, the admin would set the list of tags that would be displayed as a label in the user dashboard.

This is how would look like the dashboard

• with only "Community" labels selected in the operator cluster config

  showDevfileTagsInLabels: : ["Community"]

• having all the devfiles from the community marked with the tag "Community"

Here are few subtasks to achieve that:

• Have an operator configuration option “showDevfileTagsInLabels” to define a list of tags to display as a label. and make it available to the dashboard.
• Visually display tags labels in the dashboard get-started page for devfile with tags listed in “showDevfileTags”
• Mark with the tag "community" to all the devfiles coming from the default devfile registry

[benoitf]

isn't it conflicting with #19633 ?
AFAIK operator will be able to explicitly give a name to a given devfile registry and it will be in a dedicated section
cc @sleshchenko

[sunix]

@benoitf maybe, but this is definitly required in any case to display things such as supported architectures, etc.

[sleshchenko]

@benoitf maybe, but this is definitly required in any case to display things such as supported architectures, etc.

@sunix Why? Che Cluster is run on a particular architecture, we even should not display devfiles that are not supported on the current architecture.
Update: OK, it's not about displaying arch, but about filtering it and not displaying.

[vitaliy-guliy]

A googledoc, describing the feature https://docs.google.com/document/d/13WPTD-dGX5duq-QpTXXCFHTPe7ZrBStjbNdY71llMw8/edit#

[nickboldt]

Required for implementing UDI image (if we want to have ALL the tech preview and GA supported stuff in the same container).

See:

• Universal Developer Image devfile/api#616
• https://issues.redhat.com/browse/CRW-2463
• https://issues.redhat.com/browse/CRW-2464

Escalating to P1.

[nickboldt]

PRs to add tags to meta.yaml so we can use that data to display labels on devfile tiles:

• chore: #19953 add community tag to meta.yaml che-devfile-registry#523
• chore: #19953 add tech-preview tag to meta.yaml redhat-developer/devspaces#632

[l0rd]

@ibuziuk the milestone for this issue is 7.40 (release tomorrow) but there is no sprint/current label. Should it be moved to milestone 7.41?

[l0rd]

@ibuziuk I think we are still missing the dashboard part of this. I have set the milestone to 7.41, feel free to set another milestone if you are not going to work on it during this sprint.

[ibuziuk]

we are tracking this issue as part of #19633

[benoitf]

@ibuziuk 7.41.0 release will be cut today. This issue is not yet closed, so please close it if it's done or move it to 7.42

[nickboldt]

I see #19633 is resolved via eclipse-che/che-dashboard#432 so ... can we close this one too?

[nickboldt]

Followup in #20976