Posted: 21 Feb 2020 14:33 EST Last activity: 22 Feb 2021 2:07 EST
Deployment Manager pain points
Deployment Manager community,
In another thread I had asked for your succes stories. Now I'd like to give an oportunity to tell us about things that could be better. Please share examples of tasks you've wanted to complete using Deployment Manager which were overly challenging or just not possible. Some requests are likely on our roadmap and we can set expectations of when we expect them to be addressed, while others we may not have been aware of.
This is not intended as a place to report feature bugs, those should go through the normal support channels.
***Edited by Moderator Marissa to update platform capability tags****
Being able to run static assembler from CI/CD pipeline, at least on production environment
Sometimes our clients works with third orchestration server, like jenkins or Azure DevOps. New DM APIs are really usefull to integrate these third tools with Pega, being able to run a CI/CD pipleine throuth the Rest API. I missed being able to configure in any way a callback to the third orchestration server whith CI/CD DM result, either is a success or not.
Being able to configure approval from third tools, eg. calling an external web service and processing the response as an async callback.
What is the use case for #1, reducing FUA? This is not something we're considering at this time.
As far as callbacks when a DM CI/CD task or pipeline has completed, we are considering a message bus which supports publish and subscribe to DM topics, but that's further in the future. In the interim you could solve this by polling the DM.
The plan is to continue to extend the API's to support every action which is possible via the UI, which would include automated approval. You'll see this support grow over the next 6 months to a year.
Allowing the Pipeline to run the Multiple Deployments i.e. Case Wise processing of the deployments.
Currently, the Deployment Manager does not support the Parallel deployments due to the Single thread approach followed. Will be very helpful if we can get a case type kind of processing on top of the deployment manager which will ease the approval process.
@AbdulQaderM completely agree! Not having the ability to run multiple deployments on the same pipeline in parallel means more manual work during releases. This will be a great feature if enabled in future versions of the product.
Customer has more than 5 environments and would like to have the ability to customize the name of each of the stages in the pipeline. For example, pipeline DevSITUATPRE would have stage names of Dev, Sit, UAT and Pre whereas another pipeline for DevSITUATPPE would have Dev, Sit, UAT and PPE