We are in the process of upgrading to Pega Cloud and implementing Pega Deployment Manager. As part of this we have identified the following key steps within Pega.
Install Deployment Manager service
Enable required rulesets and privileges
Create application pipelines (defining stages such as Dev → QA → Staging → Prod)
Could you please confirm what dependencies exist outside of Pega that we should account for such as authentication setup, external repository integration or any other prerequisites?
Outside of Pega, the main dependency you must set up is a supported artifact repository and connect all Route to Live environments to it, because Deployment Manager stores and moves application artifacts through that repository. You also need authentication and access in place so Deployment Manager can reach each environment and the repository without permission issues. Make sure your network and firewall rules allow communication between the Deployment Manager service, the target environments, and the repository endpoint. Confirm that each pipeline environment is already available, correctly mapped, and ready for deployment before you build the pipeline. In simple terms, the one complete setup path is: prepare the repository, access, and environment connectivity first, then install and configure Deployment Manager inside Pega.
If you have any custom tasks, they should be considered as part of the implementation. Previously, with Pega Deployment Manager, custom tasks were created on the orchestration side. However, with Deployment Manager service (DMaS) those tasks should be reviewed and updated so they can be deployed on the candidate systems. Also you wont be able to access Dev Studio in DMaS.