Previous version files compiled in S3

[richard015ar]

In S3 we are not moving or removing previously compiled files. In that way previous releases are accessible via browser.

Example: https://dev.pressbooks.directory/js/app.140e7aa2.js This file is obsolete and was deployed on Aug, 2020.

• [x] Create a folder structure for previous releases and leave accessible only the current version of the application for each S3 Bucket (dev, staging, master-qa and production). See: https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-simple-s3.html - Versioning section
• [x] Implement the structure for dev, staging, master-qa and production S3 Buckets.

[richard015ar]

I did it using S3 versioning feature. I changed the file names of the built files, to keep those with the same name, in that way rather than have multiple different names in our buckets, each one corresponding to a different file version, now we have the same files name but with different versions, ready to rollback when is needed. There are multiple ways we could implement a rollback action, I created an issue to discuss and solve it: https://github.com/pressbooks/pressbooks-book-directory-fe/issues/214

From now, we will track different versions of the objects in the bucket. I created a life cycle rule for each bucket what removes previous versions of the objects with >= 90 days (we can change that if necessary).

The versioning feature and life cycle were created for our Dev and Staging buckets. I will leave this task Pending and assign it to @ho-man-chan, so we can review it and bring any concern / opinion before apply it to Production S3 Bucket.