-
Feature Request
-
Resolution: Done
-
Major
-
7.0.2.GA
-
2018 Week 36-38, 2018 Week 39-41
RFE details:
- Proposed title of this feature request:
PAM on OpenShift integration with external GIT repository.
- What are the nature and description of the request?
To Allow PAM on OpenShift to integrate with an external GIT repository.
- Why does the customer need this? (List the business requirements here)
1) To leverage our existing corporate GIT environment, and reduce the number of GIT servers in enterprise.
2) To allow process source assets to be kept seperate from the application.
3) To allow easy access to git repos (the internal git server of PAM is cumbersome on Openshift).
- How would the customer like to achieve this? (List the functional requirements here)
Use an external git repository instead of the internal PAM git repository
- For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented:
Test connecting the external git repository to PAM. ensure that PAM assets are stored and fetched from this repo
- Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
n/a
- Would the customer be able to assist in testing this functionality if implemented?
Yes
- is blocked by
-
RHPAM-1452 RHPAM maven repository id should be configurable instead of generated
- Closed
- is related to
-
RHPAM-1531 PAM7 PaaS image does not allow to push maven artifacts through remote repositories
- Closed
- relates to
-
RHPAM-1296 Git hooks support for imported projects
- Closed
-
RHPAM-1491 GIT_HOOKS_DIR parameter not exposed in RHPAM templates
- Closed