AEMaaCS Back copy content from Production to Stage / Dev environment

[#1]

Request for Feature Enhancement (RFE) Summary:	Option to easily replicate content on the Prod author and publisher to Stage or Dev
Use-case:	We want Stage or Dev environment to be in sync with Prod content, to be in more or less same state.
Current/Experienced Behavior:	At the moment we can use copy content sets, but that is only possible to author instance, and when we copy content set, copied pages or assets dont have the publications status.
Improved/Expected Behavior:	Copy content sets on author and publish instance, and assets and pages to have the same data from Prod to other stages
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS
Customer-name/Organization name:	CSS KRANKEN-VERSICHERUNG AG
Screenshot (if applicable):
Code package (if applicable):

[#2]

you can create 1 sling job to check the updated and modified content on the production environment daily using Query builder API.

Retrieve all the content and create the package content programmatically.

Create Package

curl -u <user>:<password> -X POST http://localhost:4502/crx/packmgr/service/.json/etc/packages/mycontent.zip?cmd=create -d packageName=<name> -d groupName=<name>

Build Package

curl -X POST http://localhost:4502/crx/packmgr/service/.json/etc/packages/mycontent.zip?cmd=build

Once that package is created you can push it to dev /stage /qa environment using CURL call .

Replicate package

curl -u <user>:<password> -X POST http://localhost:4502/crx/packmgr/service/.json/etc/packages/my_packages/test.zip?cmd=replicate

I hope above solution will work

[#3]

@RisteKo1 

Thanks for proposing this idea.

This has been reported to the engineering under the internal reference SITES-29239. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.

[#4]

Hi,

The curl idea is one that I think most people would think to try first. However, the problem is that there will be timeouts on AEM as a Cloud Service for the package handling. You can create package, but the request will timeout and there's not a good way of knowing if the package has finished being created or installed.

@RisteKo1 -

• What is the use case for having all content in sync on a lower environment?
• Does your validation team validate every page in non-production for regression work?
• How important is it to have all of the content instead of a smaller, well-structured test suite of content that's used for validation?

Looking forward to your feedback!