-
Story
-
Resolution: Done
-
Normal
-
None
-
8
-
False
-
None
-
False
-
SECFLOWOTL-98 - Promote Multi-source application feature to GA
-
-
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
- links to
-
RHEA-2024:137049 Errata Advisory for OpenShift GitOps v1.14.0