Blank window due to conflicts with the cached assets

[AlexRuiz7]

Wazuh	OpenSearch	Rev	Security
4.3.6	1.2.0	4xxx	-

Browser
Chrome, Firefox, Safari, etc

Description

This issue has been affecting our plugin for a long time. We need to investigate how to solve this issue in order to refresh the assets cache when necessary, this is, when the version of the cached assets and the actual plugin version do not match, for example, after a plugin update.

For other team members, check this conversation in Slack.

Kibana

We researched how the cache versioning works in Kibana, and found out that there was an issue with it, being fixed in Kibana 7.13.0.

• Related issue in Kibana:
  • [Webpack] The numeric prefix for cache busting in URLs to static resources does not change even if plugin code changes elastic/kibana#94951
  • Included in Kibana v7.13.0

For older versions, our plugin notifies the user with a toast, indicating that there might be a problem with the cached assets, and that a clear refresh is required.

For versions newer than 7.13.0, the assets are properly cached using the plugin build number, so no toast is shown.

OpenSearch Dashboards

As OpenSearch was forked from Kibana at v7.10.2, this fix wasn't included. They have an issue on their repo about this matter, being fixed in OSD v1.3.1.

• Related issue in OpenSearch:
  • Cache buster broken for releases opensearch-project/OpenSearch-Dashboards#1363
  • Included in OSD v1.3.1, and back ported to previous versions.

As Wazuh currently uses the OpenSearch 1.2.0 stack (indexer + dashboard), this issue is present in our OSD - Wazuh Dashboard plugin. A toast must be shown to notify the user about this.

However, the PR that fixed the broken cache buster on OSD do not take into account the plugins, but the platform itself. So, using different Wazuh versions with the same OSD version will result in conflicts with the plugin's cache. The buildNumber in the package.json from OS defines how the cached assets are used, as seen in this PR.

Proposed solution

We need the @wazuh/cicd team to change the OSD build number on the package.json with a unique number for each Wazuh version, using the Wazuh version itself or the App revision number.

PoC

[AlexRuiz7]

The solution by @wazuh/cicd proves to change the build number used by OpenSearch for assets caching.

Different versions of Wazuh will use now different build numbers, and consequently, different URLs, so this problem should not happen again. However, we'll keep watching this issue for whatever it might happen.

Below, a screenshot can be seen as evidence. Note the number 440 in the URL. The number represents the version of Wazuh: 4.4.0 (test package).