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

operator authors have a path for automated catalog updates after bundle publishing

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.14
    • openshift-4.14
    • None
    • FBC: PublishAutoUpdates
    • Strategic Product Work
    • False
    • None
    • False
    • Not Selected
    • Done
    • OCPSTRAT-586 - [Pilot phase] Enable managing releases with the file-based catalog for Red Hat Operator teams with RHTAP
    • OCPSTRAT-586[Pilot phase] Enable managing releases with the file-based catalog for Red Hat Operator teams with RHTAP
    • 0% To Do, 0% In Progress, 100% Done

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      Why is this important?

      • Given that operator publishing becomes a two-part process after switching to FBC, reducing the iterative manual effort to maintain catalog contributions over the lifecycle of the operator has the potential to significantly reduce adoption friction.  Automatable (e.g. gitops) approaches are the goal.

      Scenarios

      1. author publishes new bundle which uses raw FBC for contributions
      2. author publishes new bundle which uses basic veneers for contributions
      3. author publishes new bundle which uses semver veneers for contributions
      4. author publishes new bundle which uses the composite veneer from OSDK-2591

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rh-ee-jkeister Jordan Keister
              rh-ee-jkeister Jordan Keister
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: