Browser cache when delivering a custom kibana plugin

Elastic Stack Kibana
1

Hi,

this is about kibana and browser cache when delivering a custom kibana plugin regulary into production.

we have a custom kibana plugin and integrated it into our CI/CD. when it comes to production, browser clients are always stuck at old versions until every browser cache is cleared manually. We are wondering how we can configure kibana to get new versions delivered to clients without getting caches cleared. since there was so much progress on the kibana platform, maybe there is some trigger/configuration. it would also be ok, the get client load all kibana content with some trigger. Maybe there a way to change the identifier where bundles reside in .../36136/bundles/....

There is not even a chance to change Cache Control header directly in kibana (any special reason why that is hardcoded to 1 year)?

Thanks in advance.

2

Hi @weand you can track the progress in this issue [Webpack] The numeric prefix for cache busting in URLs to static resources does not change even if plugin code changes · Issue #94951 · elastic/kibana · GitHub

Maybe there a way to change the identifier where bundles reside in .../36136/bundles/... .

As a workaround, you can change build.number in package.json file

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.