How to deploy two codebase without overriding in AEM cloud?

[Mario248]

I have a repo A which has /apps/abc and I also have one more repo B which is having /apps/xyz. When I deploy a repo A code using cloud manager pipeline and it deploys the code /apps/abc and then when I deploy repo B, it removes /apps/abc and deploy only /apps/xyz. 

I checked the filter.xml and found that it does not have any mode so hence I added mode = merge but even after mode is merge it still overrides the others

Repo A

<filter root="/apps/abc" mode="merge" />

Repo B

<filter root="/apps/xyz" mode="merge" />

Note - I don't have this issue in my local AEM. I keep deploying these two repos and I don't see this issue at all. It is happening only in AEM cloud instances.

[Harwinder-singh]

@Mario248  You need to create a multi tenancy project from a AEM project archetype and add your individual project tenants as modules inside. More on this :

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

https://blog.developer.adobe.com/hosting-multiple-tenants-on-aem-815c8ed0c9f9

[Mario248]

Like mentioned in the above doc, I already updated the filter.xml. In fact the location is completely different /apps/abc and /apps/xyz so there should be any conflict. I dont see this override issue in local aem server and it is happening only in AEM cloud.

[arunpatidar]

Cloud manager on AEMaaCS, does a clean deployment. that means the old instances/container is deleted and new instances is added and then deployment happens.

You have to install both the code base as part of single deployment.

https://www.initialyze.com/insights/handle-multiple-projects-with-cloud-manager 

[Mario248]

Thank you. I will try to merge both repo into single repo. Is there any adobe doc "old instances/container is deleted and new instances is added " ?

[arunpatidar]

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/introduction/architec...

[aanchal-sikka · Accepted solution]

Hello @Mario248 

In case of Cloud, when code is deployed an AEM Image is created. It only contains mutable content (/content, /conf etc) from current AEM instance.

All code deployed in immutable areas like /apps are not carried over to the Image.

Thus, when you deploy /apps/xyz after deploying /apps/abc, the /apps/abc is not present in AEM Image.

In such cases, multiple repositories can be created for Project-ABC and Project-XYZ. But, these need to merge under a single parent project in cloud manager for deployment (kind-of multi tenant set-up).

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

[Mario248]

Thank you for your input. I will try to merge both repo into single repo

[Som_Adobe]

Hi @aanchal-sikka,

Can you please recommend how do we manage multi-tenancy approach for RDEs ? We are dealing with 40 applications as tenants to a parent aggregator using Git submodule approach and are analyzing perspectives to use AIO CLI commands for RDE deployment. If we plan for CLI to be executed on the aggregator then the whole purpose of RDE and quicker feature development is lost. The deployment time is over an hour every time. There can be grouped aggregators but we are looking for something really quick and easy for developers daily dev activities so that the speed of delivery doesn't get affected significantly. Please share your thoughts.

Best Regards.

[arunpatidar]

Hi @Som_Adobe 

RDE comes with the cost. I would suggest to use RDE when you need to test integration directly within environment. I would suggest not to use RDE for all kind of development work.