Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1853

location of the Get Started devfiles is not calculated correctly if external devfile registry is specified

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      = The location of the *Quick Add* devfiles is not calculated properly when an external devfile registry is specified

      When building the devfile registry, the build process updates the devfiles to set the source location of the artifact archives. When specifying multiple registries, the build process doesn't update the archive source location in the devfiles properly.

      .Deployment using multiple registries
      ====
      The Developer Sandbox enables the community registry and the {prod-short} registry.
      ====

      .Workaround

      * Specify one unique registry when building the registries.
      Show
      = The location of the *Quick Add* devfiles is not calculated properly when an external devfile registry is specified When building the devfile registry, the build process updates the devfiles to set the source location of the artifact archives. When specifying multiple registries, the build process doesn't update the archive source location in the devfiles properly. .Deployment using multiple registries ==== The Developer Sandbox enables the community registry and the {prod-short} registry. ==== .Workaround * Specify one unique registry when building the registries.
    • Not Required

    Description

      Currently, devfile-registry for CRW update all the 'devfies' during the build process and update the source location to zip based on the DEVFILE_REGISTRY_URL env var:

       

      https://github.com/redhat-developer/codeready-workspaces/blob/crw-2-rhel-8/dependencies/che-devfile-registry/build/scripts/cache_projects.sh#L54

       

      However, it does not seem to work correctly if multiple registries are specified e.g. for Developer Sandbox the community registry is enabled together with product one:

       

      devfileRegistryUrl: "https://codeready-codeready-workspaces-operator.apps.sandbox-stage.gb17.p1.openshiftapps.com/devfile-registry https://eclipse-che.github.io/che-devfile-registry/7.30.0/"
       
      this setup resulted in the non working setup where during the update the internal IP is used: 
       
      ```
       {{- name: quarkus-quickstarts
      source:
      location: 'http://172.30.189.177:8080/resources/quarkus-quarkus-quickstarts-main.zip'
      type: zip}}
      ```
       
      More details in the 
      https://github.com/eclipse/che/issues/19853

       

      Attachments

        Activity

          People

            vsvydenk Valerii Svydenko
            ibuziuk@redhat.com Ilya Buziuk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: