Why does Deployment Manager require the use of a repository manager?
Deployment Manager requires the use of a repository manager to publish and store application artifacts (product rule archives). There are a few reasons why having a dedicated application artifact repository manager is important.
- Providing stable and reliable access to repositories
- Repository tools such as JFrog Artifactory can be configured to be highly available
- No single point of failure
- Accommodate large load burts
- Supporting a large number of common binaries across different environments
- Scales with the number of binaries
- Manages them across all the different environments without creating multiple copies
- Security and access control
- Implement a security policy that prevents un-validated applications from leaking out to production
- Artifactory provides capabilities such as virtual repositories
- Integration with LDAP, SAML etc
- Complete logging - Tracing any action done to a file back to the user
- Transferring a large number of binaries to a remote location
- Managing infrastructure configuration across different environments
- You can read more in detail about the benefits of a repository manager directly from JFrog
This is a frequently asked question about Deployment Manager. Find more answers here.
Keep up to date on this post and subscribe to comments
- How to configure GitHub as a repository for Deployment Manager?
- Can we use GitHub as custom repository for Deployment Manager?
- How to set file data on pyContents of D_pxNewFile for custom repository used in DevOps/Deployment Manager?
- What versions of the Pega Platform is required by Deployment Manager?
- is Rule rebasing required with Pega Deployment Manager?