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

Support upstream plugin update automation in CRW

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      = Support upstream plug-in update automation

      // Cause:
      The plug-in `id` fields no longer contain the plug-in's version. Instead, all plug-in `id` fields use `latest` to denote the plugin version. For example: `golang/go/0.16.1` becomes `golang/go/latest`.

      // Consequence:
      Some devfiles may not start and will need to be revised. If a devfile was dependent on a specific plugin version in the `id` field, then changing the version to `latest` is required.

      // Result:
      Devfiles will start as expected. Manually manipulating plugin versions in the `id` field is no longer supported.
      Show
      = Support upstream plug-in update automation // Cause: The plug-in `id` fields no longer contain the plug-in's version. Instead, all plug-in `id` fields use `latest` to denote the plugin version. For example: `golang/go/0.16.1` becomes `golang/go/latest`. // Consequence: Some devfiles may not start and will need to be revised. If a devfile was dependent on a specific plugin version in the `id` field, then changing the version to `latest` is required. // Result: Devfiles will start as expected. Manually manipulating plugin versions in the `id` field is no longer supported.

    Description

      In https://github.com/eclipse/che/issues/15819 work has begun to streamline the update process for the plugin registry, including:

      We should enable the same behaviour in CRW so that we can also generate and validate PRs for plugin updates.

      HOWEVER...

      we should also remove all digests from meta.yaml and devfile.yaml so that we no longer have to rebuild the registry EVERY TIME a referenced container is rebuilt. Why? Because without this we'll never be able to use Freshmaker to respin containers for CVEs automatically, and will forever have to manage security issues manually.

      Failing that, could we use the RELATED_IMAGE_* env vars from the operator metadata's CSV? that way we only have a single manifest of the images, and don't have to have digests hardcoded in multiple places.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. CRW-1792 Nightly CRW tries to use eclipse/che-theia/next, but only eclipse/che-theia/latest is available

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. CRW-1275 Insert midstream copies of pkgs.devel repos where content is generated from upstream

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CRW-1621 migrate to template job + sync.sh

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CRW-668 Provide orchestration job to trigger all CRW images

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CRW-1534 Ensure that GH repo polling works as expected in main-jenkins jobs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users CRW-975 Initial support of Devfile 2.0 specification

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-1567 Sync & transform upstream Che registries into CRW registries (filter out content, support multiarch container swaps for openj9)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Activity

            People

              ericwill@redhat.com Eric Williams
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: