Design

https://marvelapp.com/prototype/7914f80/screen/92137207 

Epic Goal

Add multiple sources support to ArgoCD Discovered apps and AppSet apps.

Why is this important?

This is the most requested feature from users.

Scenarios

• Figure out how the new template source vs sources work. Does it only support one field at a time? What happens when both fields are present in the YAML?
• App table multiple repos in resource column similar to appsub for ArgoCD Discovered apps and AppSet apps
• Appset create wizard support adding multiple resources
• Appset/ArgoCD discovered app topology support multiple resources maybe similar to appsub multi-subscription support?

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. ...

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>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• [ ] FIPS Readiness
• [ ] Works in Disconnected
• [ ] Global Proxy Support
• [ ] Installable to Infrastructure Nodes
• [ ] No impacts to Performance and Scalability
• [ ] Backup and Restorable