We had to immediately roll back a change we deployed, because i18n messages weren't showing. Similar to T301461, this is likely a caching issue and we simply shouldn't cache those i18n files.
Description
Details
Related Objects
Event Timeline
Change #1161517 had a related patch set uploaded (by Jakob; author: Jakob):
[operations/puppet@production] Don't cache i18n json files in WDQS UI
Change #1161517 merged by JHathaway:
[operations/puppet@production] Don't cache i18n json files in WDQS UI
jakob opened https://gitlab.wikimedia.org/repos/wmde/wikidata-query-gui/-/merge_requests/31
Don't cache i18n json files in WDQS UI
Change #1161883 had a related patch set uploaded (by Jakob; author: Jakob):
[operations/deployment-charts@master] wikidata-query-gui: Bump query-gui image version
Change #1161883 merged by jenkins-bot:
[operations/deployment-charts@master] wikidata-query-gui: Bump query-gui image version
jakob merged https://gitlab.wikimedia.org/repos/wmde/wikidata-query-gui/-/merge_requests/31
Don't cache i18n json files in WDQS UI
Change #1161892 had a related patch set uploaded (by Jakob; author: Jakob):
[operations/deployment-charts@master] wikidata-query-gui: Bump query-gui image version
Change #1161892 merged by jenkins-bot:
[operations/deployment-charts@master] wikidata-query-gui: Bump query-gui image version
This is working now which confirms that the corresponding config in operations/puppet isn't used.
$ curl -sI https://query.wikidata.org/i18n/en.json | grep -i cache-control cache-control: no-cache