Run the S3 Deploy GH Action to redeploy the master branch
Observe the translation change made
Expected Result
The changed translation is visible in production
Actual Result
The original translation is visible in production
Notes
This is due to two different issues:
The S3 Deploy script is only invalidating index.html. This is because it is assumed that all other files are named with a hash to indicate their version, providing automatic cache invalidation when the files' contents change.
The translation.json files do not contain such a mechanism.
To address, we'll need to ensure that either (a) the translation.json files are explicitly invalidated during deploys (this might incur additional AWS costs), or (b) ensure that the translation.json file names are appropriately versioned. We'll need to investigate how to accomplish this with i18next.
Reproduction Steps
masterbranchExpected Result
Actual Result
Notes
This is due to two different issues:
index.html. This is because it is assumed that all other files are named with a hash to indicate their version, providing automatic cache invalidation when the files' contents change.translation.jsonfiles do not contain such a mechanism.To address, we'll need to ensure that either (a) the
translation.jsonfiles are explicitly invalidated during deploys (this might incur additional AWS costs), or (b) ensure that thetranslation.jsonfile names are appropriately versioned. We'll need to investigate how to accomplish this with i18next.