Overwriting of PathFactory Packages by Project Pipeline in AEM Cloud

[naruk89179065]

We have two separate pipelines in AEM as a Cloud Service — one for deploying PathFactory packages and another for deploying our main project code. However, when the project pipeline runs, it replaces or overwrites the existing PathFactory packages located in the app folder.

@SantoshSai  @arunpatidar  @giuseppebag  @konstantyn_diachenko  @muskaanchandwani 

[arunpatidar · Accepted solution]

Hi @naruk89179065 

This behavior is expected. During each deployment, Cloud Manager terminates the existing pod and spins up a new one to deploy the updated code.

You have to deploy everything together via single pipeline.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/managing-code/gi... 

[partyush]

Hi @naruk89179065 

In AEM as a Cloud Service, deployments are managed through Cloud Manager’s CI/CD pipelines. Each pipeline deploys a single "all" package, which contains all the application code (immutable content) intended for the /apps folder. Here’s the key point:

• When the PathFactory pipeline runs, it deploys its "all" package, installing the PathFactory packages in /apps.
• When the main project pipeline runs, it deploys its own "all" package, which replaces the entire contents of /apps with the main project code overwriting the PathFactory packages.

This behavior is by design: AEM as a Cloud Service treats /apps as immutable content, and each deployment fully replaces the existing content in that folder with the contents of the new "all" package. Running two separate pipelines targeting the same immutable area (/apps) in the same environment naturally leads to this conflict.

To resolve this, you need to combine the PathFactory packages and your main project code into a single "all" package and deploy them together using one full-stack pipeline. This ensures that both sets of code are installed simultaneously, avoiding any overwriting

• A single "all" package can include multiple subpackages (e.g., your main project code and the PathFactory packages).
• When deployed, this combined package installs everything at once, preserving both codebases in /apps without one replacing the other.
• This aligns with AEM as a Cloud Service best practices, where all application code for an environment should be managed through a unified deployment.

Thanks

Partyush

[naruk89179065]

thanks @partyush 

[Randeep_virk]

You can use Submodules here :- 
Parent Module having two sub modules 
 1. PathFactory packages 
 2. Main project code
Simply comment out the submodule which you are not deploying in the Parent Module POM.
By this way you will have single pipeline which manages both sub modules, separate pipeline removes folder from other pipeline.
Refer to below link for more details
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/managing-code/gi...