Deploying multiple project in AEM cloud instance

[sonuk85184451]

please help on below query - 

i have two projects needs to be deployed in AEM cloud instance  

but each time when i deploy either of the project , app folder is getting over written 

for example - when i deploy pipeline for demosite then /apps/demosite folder overwriting /apps/wknd folder

similarly when i deploy pipeline for wknd project then /apps/wknd folder overwriting /apps/demosite folder

i need both apps folder to be there both project are in different GIT repo also different adobe GIT repo

what can be the issue ? 

[Anudeep_Garnepudi]

@sonuk85184451 

Update the filters.xml (ui.apps/src/main/content/META-INF/vault/filter.xml) accordingly. 

[sonuk85184451]

can you provide an example please 

[Anudeep_Garnepudi]

Keep paths which you want to deploy in filter.xml

Check both filter.xml files from each repo.

Example: 

repo 1 filter.xml has /apps/demosite and /apps/wknd and if you to deploy only /apps/demosite from this repo then remove /apps/wknd from filters. Similarly in other repo as well.

[Himanshu_Singhal]

Hi @sonuk85184451 

I'm hoping since you're having 2 projects, that most likely could be in 2 different repos. 
If so, the best possible approach is to deploy via GIT submodule. 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

What happens is when you start deployment, cloud service build image step takes fresh image every single time and builds /apps so whatever it was previously is wiped off and takes latest code from project.

So, if you're going to deploy 2 projects separately then it's going to wipe the repo with existing ones and deploy the one which is present in current repo. 

With Git submodule approach - it binds multiple repos in single project and deploy both at same time hence both projects are going to be present during deployment. 

[Pawan-Gupta]

Hello,

If you created separate projects in different GIT the deployment will override the previous one. to overcome this better create both projects as sub module suggested by others and make it under by creating a parent project. 

like project C has sub modules like A & B. hope this works.

[Peter_Puzanovs]

Hi Sonuk,

As per today's Cloud solution[Q1 2023], you need to marry all projects together for the deployment to cloud environment [1]

[1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-... 

Regards,

Peter

[Jagadeesh_Prakash]

@sonuk85184451  I recommand you to create a project from AEM cloud architype repo and put your projects as a module in it. 

this is a multi tenant project and all the code will be deployed seperatly in a single instance.

Only confusion you will have is on the dispatcher, So you need to write a common dispatcher module seperatly. 

https://experienceleague.adobe.com/docs/experience-manager-learn/assets/deployment/multitenancy-conc...

https://levelup.gitconnected.com/aem-multitenancy-running-multiple-websites-on-a-single-aem-environm...

[HasanKh1]

Hello

What if we have to deploy only repo1 and not touch repo2.

Can we still achieve this with submodule approach?

[Aditya_Chabuku · Accepted solution]

Hi @sonuk85184451 , you can follow the suggestions given below by Community Members and one or the other approach may best suit your requirements.

I'm adding up a link how we did the AEMaaCS setup for future references. https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-... 

Thanks,

Aditya Chabuku