@mikeetiuPH @jsalanga  If you have a custom processing profile assigned to a folder, the reprocess popup shows the option to just reprocess based on that PP The docs weren't updated after we added the writeback feature, but it is supported in Cloud Service. If you don't care to writeback metadata, ...

I would open an issue on the archetype GH issue, and also do the updates manually on the project.

Unfortunately, I think the archetype should go back to embedding the core for each module in it's own ui.apps module and then that should be embedded in all.

23 embeds it, 24 does not.

Have you tried adding a "autoInstallPackage" profile to tenant 1 and tenant 2 ui.apps modules, then you can install them separately, instead of trying to embed them in the all package, which has the autoInstallSinglePackage profile

Not understanding the question. Shouldn't all module embed both tenant1 and tenant2?

Hi @anuragg41105887, I have no idea what the context of the support ticket was and an out of context response is a little hard to read. Either ways, you have your answer :-). FWIW, this is pretty clear from the docs and not sure if a support ticket is needed to begin with. I hope you and your family...

The ideal goal is to have automated tests, also, IMO, with multiple tenants, the sooner you catch the bugs, the better. lots of customers wait until Stage to merge all the code and deploy once, this is too late to cause issues. Deploy everything together on dev, write automated tests, catch bugs ear...

FWIW, this document explains what you are looking to do https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/creating-aem-application-project.html#environment-variables

In AEM Cloud Service, you cannot install parts of the code base, every deployment creates a new image and your complete code package has to be deployed everytime. If Cloud Service is on the roadmap already, I'd try to stick to the best practices for that. Even though it might be possible for you to ...