Uploaded image for project: 'Operator Ecosystem'
  1. Operator Ecosystem
  2. OPECO-2779

[upstream] exclude bundles with `olm.deprecated` property when rendering

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.13
    • openshift-4.13
    • None
    • False
    • None
    • False
    • OCPSTRAT-425 - Enable file-based Catalog for flexible and lightweight catalog maintenance
    • Refinement Backlog

      This is a clone of issue OPECO-2646. The following is the description of the original issue:

      Previous bundle deprecation was handled by assigning a property to the olm.bundle object of `olm.deprecated`.  SQLite DBs had to have all valid upgrade edges supported by olm.bundle information in order to prevent foreign key violations.  This property meant that the bundle was to be ignored & never installed.

      FBC has a simpler method for achieving the same goal:  don't include the bundle.  Upgrade edges from it may still be specified, and the bundle will not be installable.

      Likely an update to opm code base in the neighborhood of https://github.com/operator-framework/operator-registry/blob/249ae621bb8fa6fc8a8e4a5ae26355577393f127/pkg/sqlite/conversion.go#L80

      A/C:

      • CI/utest/e2e passes without flakes
      • appropriate documentation (all upstream) updated/reviewed

       

       

       

       

       

       

       

            rashmigottipati Rashmi Gottipati
            rh-ee-jkeister Jordan Keister
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: