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

Enable Edit mode for any source of a multi-source app

XMLWordPrintable

    • 8
    • False
    • None
    • False
    • SECFLOWOTL-98 - Promote Multi-source application feature to GA
    • Hide
      With this update, you can view and edit the source parameters of a multi-source application. The Sources tab shows all the sources that belong to the multi-source application and this is where you can perform form-based guided editing of the parameter values. This is similar to what you already can do for single source applications, but for multiple sources as well.

      See SourceTabEditAndSave screenshot
      Show
      With this update, you can view and edit the source parameters of a multi-source application. The Sources tab shows all the sources that belong to the multi-source application and this is where you can perform form-based guided editing of the parameter values. This is similar to what you already can do for single source applications, but for multiple sources as well. See SourceTabEditAndSave screenshot
    • Enhancement
    • Proposed
    • GITOPS Core Sprint 3253, GITOPS Core Sprint 3254, GitOps Tangerine - Sprint 2255, GitOps Tangerine - Sprint 3256, GitOps Tangerine - Sprint 3258

      Story (Required)

      As a user editing a multi-source Argo CD application, I want to edit any existing source of a multi-source application, using the Argo CD UI.  Currently, the one source that is shown in the UI is read-only (The Edit button is disabled).

      Background (Required)

      This is one of several stories for the multiple source support in the UI. See https://issues.redhat.com/browse/GITOPS-2654

      Out of scope

      CLI changes

      Approach (Required)

      Building on top of the changes in https://issues.redhat.com/browse/GITOPS-3977, this step will add the capability to edit any source listed under that tab.

      Dependencies

      https://issues.redhat.com/browse/GITOPS-3977 

      Acceptance Criteria (Mandatory)

      • Edit button is enabled
      • Any user changes are saved
      • The collapsible section needs to be re-layed out so that Source specific info should be in a separate Editable 'section' and parameters in another.

      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: