Betreff: Cloning of environment from PROD to STAGE or from PROD to DEV or from STAGE to DEV

[#1]

Demande de résumé des améliorations des fonctionnalités (RFE) :	Having the ability to clone one environment to another one
Cas d’utilisation :	each 3 months we have to align the environment from PROD to STAGE or from PROD to DEV for all our digital world(from STAGE to DEV and for starting project DEV to STAGE, STAGE to PROD is also usefull)
Comportement actuel/expérimenté :	today we use the feature of content copy - but it's taken around 4 days and the feature is not done for that.
Comportement amélioré/attendu :	have a feature of cloning, duration expected : less than one day
Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) :	AEM Cloud
Nom du client/de l’organisation :	Nathalie Riasse / Louis Vuitton
Copie d’écran (si applicable) :
Package de code (si applicable) :

[#2]

A very good suggestion. 

[#3]

Hi Nathalie,

Have you seen Content Sync [1] tool awesome tool by Egor?

All you need is configure ACS commons on source and target machine, once connection is established all you have to do is select the tree and submit.

Only new and modified resources will be copied.

It supports incremental updates(helps speed up copy on existing instance) and addresses many other shortcomings!

The tools is plug and play, so you can add your own copy strategy!

[1] https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html

Regards,

Peter

[#4]

@NathalieLV 

Thanks for proposing this idea

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