Question
Bradesco Seguros
BR
Last activity: 7 Jul 2022 9:00 EDT
The First Deploy using Deployment Manager
I have a big doubt regarding the use of Pipeline Deployment. When we generate the Development environment artifact and go to the next stage of the Pipeline, which is the QA environment, the first step is to perform the Deploy application step.
In my scenario, I am implementing my first Deploy, that is, the application does not yet exist in the quality environment and the package generated in the development environment contains the application that I want to implement.
I verified that, the pipeline executes the step, to apply the Deploy, however, when it goes to the next step, which is to execute the guardrail, it receives a failure, because it indicates that the Access Group to run this verification, was not found .
I have a big doubt regarding the use of Pipeline Deployment. When we generate the Development environment artifact and go to the next stage of the Pipeline, which is the QA environment, the first step is to perform the Deploy application step.
In my scenario, I am implementing my first Deploy, that is, the application does not yet exist in the quality environment and the package generated in the development environment contains the application that I want to implement.
I verified that, the pipeline executes the step, to apply the Deploy, however, when it goes to the next step, which is to execute the guardrail, it receives a failure, because it indicates that the Access Group to run this verification, was not found .
{ "pxObjClass":"Pega-Int-Pipeline" ,"pyAccessGroup":"BVTI:Authors" ,"pyApplicationName":"BVTI" ,"pyApplicationVersion":"01.01.01" ,"pyBuildName":"Dep-1TYVK1YWSR1VRH5" ,"pyExecutorActivityClass":"Pega-API-ApplicationManagement" ,"pyExecutorActivityName":"pzGetApplicationsGuardrailMetrics" ,"pyID":"Task-RI1445YS9MER5YG" ,"pyIsTaskSync":"true" ,"pyStatusMessage":"Invalid access group BVTI:Authors" ,"pyStatusValue":"FAIL" ,"pySystemNodeID":"pega-web-75479db5cd-bnl4l" ,"taskType":"CheckGuardrailCompliance" ,"thresholdGuardrailScore":"90" ,"response":{ "executorActivityClass":"Pega-API-ApplicationManagement" ,"executorActivityName":"pzGetApplicationsGuardrailMetrics" ,"ID":"RULE-APPLICATION BVTI 01.01.01" ,"pxObjClass":"Pega-Int-Pipeline" ,"stepPage":null } }
We verified that the application was not implemented, as the action should have been in the previous step, and therefore it does not identify the access group.
My main question is: Is the Deployment Manager prepared to execute the first deploy of an application, through the pipeline that is suggested for configuration? Or is it necessary to manually deploy your first Deploy, so that the application exists in the above environment as QA and Production, so that the CI|CD configuration can make sense.
I say this, because after we put the package manually and then went to apply a new package, the pipeline worked correctly.
YMGIT
LK
@GuiValino1984 One suggestion is to customize the deployment pipeline workflow. Though I agree it's only a workaround
Anamata
NL
@GuiValino1984 Just out of curiousity. What is your goal of doing a guardrail check AFTER deployment? Ofcourse there need to be some component packages installed on all the environments to do an initial deploy. Components like DevOpsFoundation. These need to be included in an (already) existing application. So some manual work needs to be done first. Michel Kraaij - van den Berg Anamata
Bradesco Seguros
BR
@Michel Kraaij I think putting it makes real sense. However, the guardrail issue is already configured by default when you define the stage tamplate for QA environment. If a manual implementation is really necessary at first, it would be interesting for Pega to make it very clear in the documentation. Although I have the opinion, that you should have the base configuration in the development environment and later in the first deploy already use the Deployment Manager to do the first installation of the application.