Epic Goal

• Move the Git credentials out of the App Lifecycle app create flow.

Why is this important?

• Maintain all of ACM credentials in 1 location, provides an easier user experience.

Scenarios

1. User can define Git connection as a credential.
2. User can create application with a git connection, and select the previously defined Git connection.
3. User can create application with a git connection, and if the Git connection does not already exist, user can click the button to define/add a new credential for the Git connection.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
•  

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions:

1. What about moving the Helm Repo connection information?
2. What about moving the Objectstore details?

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>