-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
ACM App Support Private repositories (that have a URL that typically start with git or ssh)
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
To Do
Epic Goal
...
Private repositories that require an SSH private key have a URL that typically start with git@ or ssh:// rather than https://.
this is currently not possible
Why is this important?
...
ssh/secure connections are difficult
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)
