Cloud Manager : Enabling Rollback from Previous Build Snapshots

[#1]

Request for Feature Enhancement (RFE) Summary:	Cloud Manager Deployment: Enabling Rollback from Previous Build Snapshots
Use-case:	The customer is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image.
Current/Experienced Behavior:	The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much as possible.
Improved/Expected Behavior:	The production deployment is complete. After the deployment, the customer discovered blocker issues on one of the 24 websites. They wanted to roll back the deployment. They should be able to restart the Stage/Prod deployment using an earlier stable built image.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as a Cloud (2024.4.16145.20240430T082417Z)
Customer-name/Organization name:	LG Electronics, Global HQ Korea 24 subsidiaries (UK,DE,PE,TR,JP,FR,SG,CO,SA,SA_EN,CA_FR,CA_EN,KZ,ID,IT,CL,TH,PT,IN,HK,HK_EN,BR ,MX ,PA)
Screenshot (if applicable):
Code package (if applicable):

[#2]

@kwangmin 

Thanks for proposing this idea

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