If you have been provisioned Deployment Manager on Pega Cloud, you should use the pegacloudcustomerroot repository. This will be automatically configured for you and should not need to be specified in the pipeline. Please see the instructions for referencing repositories in the pipeline as part of the help for additional information.
I can't browse through the repository. I need to browse through the repository to select the artifact during the import. I am not able to view the artifacts in import wizard. The same repository when configured in pipeline I am able to view and select the artifact and deploy. Is there any specific configuration I need to make, so that it visible during the import process?
Posted: 1 year ago
Posted: 19 Aug 2020 23:43 EDT
Anil Kondakindi (konda)
Senior Manager, Cloud Engineering
Import/export wizard and deployment manager publish/fetch artifacts from different path locations in the repository. The import wizard looks for artifacts based on the type. for eg: for branches it looks for artifacts in the path <repo>/branches, for products <repo>/products etc. But deployment manager has dev and production repositories and publishes artifacts by pipeline name and application name and version. If you are already using deployment manager then you could deploy any of the previously generated artifact from the pipeline using the 'Deploy Existing artifact' option when triggering a new deployment.
The pipeline deployments would give a consistent deployment approach by ensuring all the quality gates are passed before the change gets to production. What is the use case to switch to import wizard for deploying artifacts generated from deployment manager pipeline?
Posted: 1 year ago
Posted: 19 Aug 2020 13:58 EDT
Srikanth Pothkanuri (poths1)
Principal Cloud Development Engineer