Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-1974

ProjectHelmChartRepository display name (spec.name) is not used in Helm Charts catalog

XMLWordPrintable

    • Moderate
    • None
    • ODC Sprint 225, ODC Sprint 226
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

       

      When creating a ProjectHelmChartRepository (with or without the form) and setting a display name (as `spec.name`), this value is not used in the developer catalog / Helm Charts catalog filter sidebar.

      It shows (and watches) the display names of `HelmChartRepository` resources.

      Version-Release number of selected component (if applicable):

      4.11

      How reproducible:

      Always

      Steps to Reproduce:

      1. Switch to Developer Perspective
2. Navigate to Add > "Helm Chart repositories"
3. Enter "ibm-charts" as "Chart repository name"
4. Enter URL https://raw.githubusercontent.com/IBM/charts/master/repo/community/index.yaml as URL)
5. Press on create
6. Open the YAML editor and change the `spec.name` attribute to "IBM Charts"
7. Save the change
8. Navigate to Add > "Helm Chart"

      Actual results:

      The filter navigation on the left side shows "Chart Repositories" "Ibm Chart". A camel case version of the resource name.

      Expected results:

      It should show the "spec.name" "IBM Charts" if defined and fallback to the current implementation if the optional spec.name is not defined.

      Additional info:

      There is a bug discussing that the display name could not be entered directly, https://bugzilla.redhat.com/show_bug.cgi?id=2106366. This bug here is only about the catalog output.

       

        1. Screencast from 10-13-2022 041234PM.webm
          1.78 MB

              dsantra12 Debsmita Santra
              dsantra12 Debsmita Santra
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: