Migration of assets from archive folder
Overview
As part of the migration from Amplience to Cloudinary, we lazily migrated assets from across the website into the archive folder in Cloudinary. The assets that were migrated include the manequin and triptych assets for thousands of product SKUs. Whilst the assets are in the archive folder they are not synced with Hybris via our automated workflow. This means that if those assets need updating or reordering, they would need to be deleted from Hybris and reuploaded to Cloudinary. We looked into the feasibility of automating the migration of mannequin and triptych assets from the archive folder to their respective folders in Cloudinary in order that they would be synced with Hybris and the Digital Merchandising team could make any updates to those assets via Cloudinary, and any changes would be reflected automatically. After our investigation, we decided that it was not feasible to migrate the assets.
Status
Accepted
Context
Full context of the investigation
Decision
We will not migrate any assets from the archive folder in Cloudinary.
Consequences
- We have averted the huge risk of updating thousands of assets on the site at once
- The archive folder continues doing the job for which it was intended; keeping assets live on the site and preventing broken URLs whilst Digital Merchandising take time to reupload assets to Cloudinary
- We will rely on the archive folder existing for longer than we would have liked
- We have had to increase the number of users that are able to access the archive folder
- During this time where more users have access to the archive folder we have less control over whether users are in fact re uploading assets or whether they are using asset URLs straight from the archive folder (this mainly applies to Digital Brand team who export URLs)