rancher/security-ui-exts on the table views branch

The Vulnerability Scanner and Runtime Enforcer extensions (main), each built twice: against the proto-supercharged-tables shell, and against the shell from just before extensions were kept off table views. The backend runs on mf-security.

Load a build

  1. Open the preview: https://rancherproto-supercharged-tables-securityr.13.48.147.135.sslip.io/dashboard/
  2. Preferences → Advanced Features → turn on Enable Extension developer features.
  3. Extensions → ⋮ → Developer Load, paste a URL below, leave Persist extension unticked.
  4. Reload the page before loading the other build.

Built against this branch

expected: the extension's own tables, as written

https://sec-ext.13.48.147.135.sslip.io/branch/vulnerability-scanner-0.9.0/vulnerability-scanner-0.9.0.umd.min.js
https://sec-ext.13.48.147.135.sslip.io/branch/runtime-enforcer-0.1.0/runtime-enforcer-0.1.0.umd.min.js

Built before the fix

expected: table views forced onto its tables

https://sec-ext.13.48.147.135.sslip.io/control/vulnerability-scanner-0.9.0/vulnerability-scanner-0.9.0.umd.min.js
https://sec-ext.13.48.147.135.sslip.io/control/runtime-enforcer-0.1.0/runtime-enforcer-0.1.0.umd.min.js

Built against this branch, opting in

expected: table views on the Registries and VEX Hubs lists, which pass :table-views="true" (the only change to the extension); its other tables as written

https://sec-ext.13.48.147.135.sslip.io/optin/vulnerability-scanner-0.9.0/vulnerability-scanner-0.9.0.umd.min.js
https://sec-ext.13.48.147.135.sslip.io/optin/runtime-enforcer-0.1.0/runtime-enforcer-0.1.0.umd.min.js