Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4647

Support multi-source (multi-revisions) in RevisionMetadataPanel

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • SECFLOWOTL-98 - Promote Multi-source application feature to GA
    • Hide
      With this update, you can view the revision history and rollback to a particular version of a multi-source application. Specifically, in the details panel, you can readily see the latest revision or commit information for each source in a multi-source application. In the History and Rollback panel, you can also see the revision history associated with each source, and choose which version to rollback to.

      See DetailsPageRevisionPanel and HistoryAndRollback screenshots
      Show
      With this update, you can view the revision history and rollback to a particular version of a multi-source application. Specifically, in the details panel, you can readily see the latest revision or commit information for each source in a multi-source application. In the History and Rollback panel, you can also see the revision history associated with each source, and choose which version to rollback to. See DetailsPageRevisionPanel and HistoryAndRollback screenshots
    • Enhancement
    • Proposed
    • GitOps Tangerine - Sprint 3256, GitOps Tangerine - Sprint 3258

      Story (Required)

      In the current rollback and history PR that is submitted by the contributor in the community, the RevisionMetadataPanel is not invokable nor is updated to support multiple sources and multiple revisions.  This story will add that support in.

      Background (Required)

      _See https://issues.redhat.com/browse/GITOPS-2654_

      Out of scope

      N/A

      Approach (Required)

      Build upon what the contributor has in his PR

      Dependencies

      https://github.com/argoproj/argo-cd/pull/14124 

      Acceptance Criteria (Mandatory)

      The details page sync status panel's More or (...) button when pressed should launch the revision panel and works for both single source apps and multi-source apps.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

            kykchong@redhat.com Keith Chong
            kykchong@redhat.com Keith Chong
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: