As a developer of Notify I would like to be confident that users are seeing the correct versions of our static assets so that we can ensure the best user experience.
WHY are we building?
When updating notify assets (images etc), they are sent to cloudfront, which caches them. A cache invalidation (#247) will ensure that it is refreshed, but this may still take some time, during which users may not be seeing the latest static images.
WHAT are we building?
Implement a SHA fingerprinting system on assets (see references in GCArticles)
Description
As a developer of Notify I would like to be confident that users are seeing the correct versions of our static assets so that we can ensure the best user experience.
WHY are we building?
When updating notify assets (images etc), they are sent to cloudfront, which caches them. A cache invalidation (#247) will ensure that it is refreshed, but this may still take some time, during which users may not be seeing the latest static images.
WHAT are we building?
Implement a SHA fingerprinting system on assets (see references in GCArticles)
VALUE created by our solution
Better user experience
Acceptance Criteria
QA Steps