Thanks Esteban, the inconsistences part makes sense. For autoscaling, if a new publisher pod spins up, where is it getting all of it's mutable content from to install into the instance?

It's an existing codebase, not something I wrote, so while I agree it isn't the recommended approach, it's how it's working today. I was more curious if Adobe is advising not to take the approach due to the possibility of repository corruption or some other major negative affect on the publishers.

It's an existing codebase, not something I wrote, so I'm not looking to do it on the publisher, I'm just looking at what already exists. While I realize it isn't a recommended way of doing it, it does appear to work and the changes do persist on the publishers. I was more curious if Adobe is advisin...

As part of the migration steps from AEM on prem to AEM as a Cloud Service: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journey/readiness It lists this item to check for: Changes to Publish repositoryDirect changes to the Publish repository are not al...