Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-7353

Update Shipwright API usage from v1alpha1 to v1beta1 when Shipwright operator goes GA

XMLWordPrintable

    • Replace v1 Shipwright build APIs from alpha to beta
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-868 - Update Shipwright API usage from v1alpha1 to v1beta1 when Shipwright operator goes GA
    • 0
    • OCPSTRAT-868Update Shipwright API usage from v1alpha1 to v1beta1 when Shipwright operator goes GA
    • 100
    • 100% 100%
    • S
    • Not Supported

      Epic Goal

      Change API designator from alpha to beta for v1 Shipwright builds.

      Why is this important

      To maintain currency with API specs

      Scenarios

      Acceptance Criteria (Mandatory)

      • Update the API designator to beta
      • Ensure Shipwright works as normal

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …
      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

            avik6028 Avik Kundu
            pdave@redhat.com Parag Dave
            Avik Kundu Avik Kundu
            Sanket Pathak Sanket Pathak
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: